I'm more experienced with developing scripted applications (PHP) for the web.
One aspect of these is you can change out the php file while the webserver is 
running. Existing connections will use the php that was loaded, new connections 
will use new PHP. And in general, these happen on a per php script basis.

How would someone do an upgrade? It seems that we have to stop everything and 
start everything for a witty application? 
Or, could witty somehow maintain more than one application at a time, and when 
a newer one comes along, be messaged to use the new one for new connections? 
And as sessions are [re]started, move to the new while current sessions remain 
on the old implementation or are signaled to gracefully restart the session. 
Also how is session data handed off between upgrades?

Many thanks in advance!
------------------------------------------------------------------------------
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to