, unfortunately.
I am trying to migrate (port) our server application to Cygwin, and it stops us
completely. It works everywhere else.
Please take a look if this is something that can be fixed quickly.
Thanks!
Oleg Moskalenko
--
Problem reports: http://cygwin.com/problems.html
FAQ:
I can write a simple test server and client programs and I'll post it here,=
in a few hours. Our existing code is just too large.
Thanks
Oleg
>
> On Thu, Apr 11, 2013 at 02:19:25PM -0700, Oleg Moskalenko wrote:
> >Hi All
> >
> >I found a non-standard beha
hu, Apr 11, 2013 at 02:19:25PM -0700, Oleg Moskalenko wrote:
> >Hi All
> >
> >I found a non-standard behavior of UDP sockets in Cygwin. Normally, people =
> do not experience it, but the communication pattern that I am going to desc=
> ribe here is often used in DTLS (ac
>
> However, I think I found a workaround on the application level.
> Apparently all packets sent to a specific address are sent to the first socket
> which has been bound to the address. If that socket has been closed, the
> next in
> line gets the packets (unless it has been connected and the
>
> Too bad. I don't know the DTLS protocol, but isn't it possible to do the
> server
> part with a single UDP socket? If you keep track of the already connected
> clients, you know if the just incoming packet is a connected or connecting
> client,
> and then you can use different threads to
5 matches
Mail list logo
