Tomasz Janczuk
Tomasz Janczuk
Good idea about wiki. I wonder if we should just add an option to `git azure init` to specify the URL of the .git-azure repository to create the submodule of...
@Kahuna64 the mechanism I outlined allows you to _understand_ what the identity of the caller is, but you cannot _impersonate_ that identity for downstream calls.
Are you calling `Edge.Func` for every HTTP request in your app? I don't see the JS code having any dependency on the request. In that case I'd recommend calling `Edge.Func`...
No, I apologize, I misread the original description. My comment above does not make sense in the context of your scenario. What you are saying here: > This call succeeds...
> just as important for us would be a way to sense that Edge might have entered this state (a timeout is difficult because we don't know how long the...
I also find infinite loops unlikely to be the root cause of the issue; I suspect there is a stress issue of some kind. Isolated repro would be very helpful...
Edge does not start an external Node process. Edge starts the Node.js event loop and V8 _within_ the CLR process and provides an in-memory interop mechanism between CLR and V8....
Hello World!
> We could go directly for the index in the error, but then risk missing some updates. @stianeikeland Why would this approach miss any updates? If any changes had been...
I think you are right; what I proposed above would not address the cases of a race condition between broken network connections and updates on the server. I would suggest...