On Fri, Dec 18, 2009 at 15:02, Javier Guerra <jav...@guerrag.com> wrote: > On Fri, Dec 18, 2009 at 6:30 AM, Fabio Mascarenhas <mascaren...@acm.org> > wrote: >> As you can see, when the coroutine finishes Copas closes *the socket >> that coroutine was awakened with*. So if you do a copas.send, it >> yields, and then you exit after coming back, Copas closes the socket >> that you sent to. If Javier is here he can tell if that is indeed the >> intended behavior or not. :-)
> I'm here. I didn't answer before because frankly i remember very > little about Copas :-) So, the Copas project is effectively not supported any more? Bad news. > but yes, Copas isn't a general purpose multitasking environment with > support for communications; it's a wrapper around select() that > associates coroutines with sockets. IOW, there's a single concept > that ties a socket and the code that handles it. > in Alexander's case, i think the best would be to add some API to tell > Copas the socket transfer between coroutines. Wouldn't it be better to hold a map of handler to connection, and close only a connection that is tied to the current handler? Thank you, Alexander. _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
