I understand that Webware is threaded instead of forking. Will there be any problems maintaining a socket connection throught a users session? The 'client' module will be doing stuff like reads and writes to the server even while the user is idle (before the session is timed out). I guess this would be similar to writing a web based front end to IRC.
You won't be able to put the socket in the actual session. See a recent thread started by Eduardo Elgueta for a little discussion of this (the thread has no subject, how annoying). It's not hard to hold onto the socket. The threaded, persistent server will probably be quite convenient for this kind of application, compared to a multi-process or asynchronous setup.
-- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
