caracostea
caracostea
@csanders-git Is there any way this can be achieved on IIS also?
Same... ``` Failed to construct REST client cannot create REST client: no client config ```
It's kind of hard to tell from your code what's happening from start to finish. Are you sending all 1000 messages on a single connection or are you creating a...
Also, are you using a single task to send all messages or a new task for each message? In my experience with TPL, I've seen that with high numbers of...
Forgot to mention that if I set different port numbers, the LocalEndPoint address is 127.0.0.1, as expected.
Yes, your findings replicate on my test machine, also. I will try to rebuild this test using the udt4 library alone, without the wrapper so we can eliminate this layer...
I was able to redo the test using only the native udt4 library (no udt-net wrapper involved) and the behavior is still present. Hence, it is a udt4 bug, not...
Still, hope we can solve this one.
I've also done a send/recv test and only one socket receives the sent bytes. The socket which receives is the one for which the advertised IP version matches the real...
Here is something that might have to do with it: http://sourceforge.net/p/udt/discussion/393037/thread/02526646/ mostly the part where it says "internally UDT does not differentiate port by protocol (v4 or v6)".