gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] multitaskhttpd experiment


From: lkcl
Subject: Re: [Gnumed-devel] multitaskhttpd experiment
Date: Wed, 14 Jul 2010 13:28:55 -0700 (PDT)

rrright, i even solved the problem of lynx not working: i made the back-end
server support HTTP Keep-Alives which i should have done in the first place.

apply these:
http://lkcl.net/gnumed/0005-add-keep-alive-version-of-list-server-directory-file.patch
http://lkcl.net/gnumed/0006-add-keepalive-version-of-send-error.-demo-showing-th.patch

then git pull on multitaskhttpd repo

then do:
$ cd multitaskhttpd
$ python proxyapp.py &

this will redirect traffic from http://127.0.0.1:8080 to
http://127.0.0.1:60001

then do:
cd gnumed/client
./gm-from-vcs.sh --ui=mtweb &

this will start up the SimpleJSONRPCServer.py on port 60001

then do python testjsonrpc.py

and you should be rewarded with two successful queries and a prompt *inside*
SimpleJSONRPCServer asking for a username and password.  this is *correct*
because there should be an exception thrown instead.

if you also browse to http://127.0.0.1:8080 you should see a listing of the
current directory, and at the bottom a "Cookie: hexdigest" shown. check also
the "send_head. pid: NNNN" number and make a note of it.  if you then
*close* the web browser down entirely and re-visit the page, you should note
that the same hexdigest is shown. also, double-check that the debug info
from SimpleJSONRPCServer "send_head. pid: NNNN" is the *exact* same number.

then, open a 2nd web browser, you should now get a 2nd hexdigest and a 2nd
pid: NNNN number.  refresh the first browser, the two should be separate,
all happy, regardless of how many times you exit the web browser(s).

l.

-- 
View this message in context: 
http://old.nabble.com/multitaskhttpd-experiment-tp29154568p29166372.html
Sent from the GnuMed - Dev mailing list archive at Nabble.com.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]