> Hello list, > > I'm just curious whether Neko socket API supports multi-threading > properly? I'm using a stress-testing client for my Apache+Neko-based > webapp, and the client is implemented in Neko. Strangely enough, it > often reports socket errors like > Custom([EMAIL PROTECTED]) > while I have a feeling that the website responds pretty ok. It might > be my Windows TCP/IP stack troubles of course, but Neko sockets and > multi-threading also look a bit suspicious.
If one socket is owned by only one thread, it shouldn't cause any problem. Crashes can occur if you are performing some operations on the same socket in different threads. The reason of socket_recv is not clear to me, it looks like the connection was stopped until all data has been sent, or that more data is being readed than available. Nicolas -- Neko : One VM to run them all (http://nekovm.org)
