Ok, the Felix webserver (in tools directory) is not behaving itself. There seems to be an attempt to write on a closed connection, after which the server just exits for unknown reason.
I note that webserver does NOT read the whole of the client's request, only the first line (the GET line). If the client closes the connection when it should be receiving data, this is OK, the webserver should handle that, not exit. I can't find any code that makes it exit, however the code for stream I/O is scattered all over the place (demux, faio, etc) and the control flow is not obvious (especially as demux is running in a pthread which releases Felix fthreads from the sleep queue). I'll get to the bottom of this..:) It is possible ALL the fthreads (including the main one) are sleeping, and that is causing the termination. Sleeping fthreads are still rooted int the gc, but I'm not sure if they're considered when Felix decides whether to terminate or not. It's not clear why the write is failing either. The server does server up one page, and sometimes one of the images (I'm using the Python reference manual as the test case and driving with Firefox.) To use the server, http://localhost:1234/somefile.html It should just work. It used to work, more or less, on Linux using epoll, except for the known bug in Posix sockets (async close is badly specified in Posix standard). -- john skaller skal...@users.sourceforge.net ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
