Elad Zelingher

The issue is not backward compatibility, but having this behavior enabled by default. This might involuntary expose internal information of the code to an attacker, which might use it to...

Hi, I'll write a detailed response once I get in front of a computer. For the meantime, see this thread: https://github.com/Code-Sharp/WampSharp-docs/issues/3 Elad On Mon, Feb 11, 2019, 07:38 CapAdv wrote:...

Please see also this StackOverflow question and answer: https://stackoverflow.com/questions/19102966/parallel-foreach-vs-task-run-and-task-whenall On Mon, Feb 11, 2019, 07:55 CapAdv wrote: > Thx. I will try the async approach. > > > Sent from...

Once the callee is done with an invocation, it creates a YIELD message which is queued to a message queue. Once this message is processed, it is serialized to the...

@CapAdv, as I explained, the response are serialized and sent to each client sequentially, i.e. one at a time (per client, it does happen simultaneously for all clients). This is...

Client = instance of IWampChannel. So in your case, if you open a WampChannel per process, then each process has its own queue on the router side, this queue is...

I looked at your code and debugged it a bit. What's happening there is that you call a procedure that runs shortly, but returns a long string, and then call...

I currently don't expose the underlying `IWampRealmProxy` so it's not possible to do this directly. You can create a `WampChannel` that uses `InMemoryBinding`/`InMemoryTransport` in order to obtain a channel and...

I don't have enough background on the problem, but you can use an authentication mechanism to verify a client's permissions upon connection establishment. See the documentation website.

I guess you should minimize the number of times you pass these on the wire. Authenticate first using HTTPS and receive a cookie. Then use cookie based authentication. Use WAMP...