Re: Witango-Talk: Silly Userreferance argument

[Anthony M. Humphreys]

Yeah, or like this example: Sometimes we must re-start Tango on our live site. The batch files that does it clears out the files that store the vars that are "supposed" to be written out to disk during a "normal" shut down, but it rarely is "normal" if we are in the need to re-start Tango.   Users on the site may get a slight interruption if they are unlucky while this happens, but a re-load later and the site's all as it was before. On one site we are lucky enough to have more than one server running so in this case users browsing our site wouldn't even notice that we did anything to the site - except that it was sped it up, or made it works properly again. ;-)     ----- Original Message ----- From: Ian Daniel To: Multiple recipients of list witango-talk Sent: Friday, May 10, 2002 7:18 PM Subject: RE: Witango-Talk: Silly Userreferance argument As Anthony pointed out in another post, it might be better (or best) to define ways of storing variables that are beyond local (or the new "request" ... vers. 5 feature) scope in the database, thus allowing for Witango servers to be added or deleted from the load group at will, without fear of losing a session.  That would be the subject of another POST.   o[;-)