Release 1.1.3 is currently being held up by a problem
with the webserver. If anyone can help by testing, debugging,
or simply inspecting the C++ code for the async handling that
would be great.

The webserver can be run by:

        bin/flx --test tools/webserver

and add --debug to get run time debugging. It makes the current
directory available as root on 

        http://127.0.0.1:1234

(Don't use the name localhost -- Firefox and other brainless
clients try to lookup the name using Google or something
if a connection fails :)

The URL which fails for me is:

        http://127.0.0.1:1234/doc/test/en_flx_regress_0003.html

Using wget, or, with firefox the display ends before the end
of the file (due to a reset connection) The file is 2.8Meg.

Relevant code is ALL of flx_async, flx_pthread, flx_faio,
flx_posixio, flx_demux... ;(

It appears the connection is being shut down somehow
before the final 64K or so of data is transmitted.

On alondra, this happens on every file.
[I.e. fetching on my local machine from the felix-lang.org
system]

IMHO this is a synchronisation problem, eg a race:
the diagnostics from the server indicate it is faithfully
sending all the right information (but of course I'm
not sure).


-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language

Reply via email to