Re: [liblo] Patch for TCP server

Hi Camille,

Thanks for the patch! I'll review it shortly, sorry I didn't get to
your email until now.

Nico: I'll take a look at shutdown.  It is called in one place, in
address.c, but somehow it did not make it into the rest of the places
where closesocket() is called.

I'm starting to pay some attention to the bug list and some features
I've been planning to implement, because I'd like to do release
relatively soon. (Meaning, within a couple of months. I'd like to say
sooner, but I'm also trying to finish a little PhD thesis on the
side!)  So if anyone has ideas / bugs fixed / features they'd like,
now's a good time ;)

Steve

On Fri, Feb 17, 2012 at 3:52 AM, Camille Troillard
<ca...@os...> wrote:
> Hi,
>
> When a liblo server is configured with a TCP socket, it manages one listening socket and a list of streaming sockets.  The code to read from TCP sockets is in server.c, in lo_server_recv_raw_stream, line 665.  In this function, is an event happened on the listening socket, we call the function accept, and then if everything went fine, proceed to reading the first packet.
>
> There is a problem that causes my application to hang while waiting for the first packet of data, just after a connection has been accepted.  In fact, once a socket is accepted, liblo should not try to read from it, but instead give up control to the application.
>
> Attached is a patch that attempts to fix that.  I hope I got the logic right.
>
>
> Best,
> Cam
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>