Sorry Roland, My last post was generalizing for everybody's sake - I didn't mean to imply that you don't get it - because I know you do :-)
I'm purposely not going to give lessons on "state" management in this thread, or HTTP. Please do your own research for those who want to know more..... -----Original Message----- From: "Scott Cadillac" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Wed, 13 Oct 2004 13:13:54 -0600 Subject: Re: Witango-Talk: Cookies > Hi Roland, > > Good one. Being Canadian, I enjoy that joke :-) > > > but the > > understanding/misunderstanding is around what witango server does > when > > confronted with an expired session identifier. > > As programmers, where we don't have intimate knowledge of the inner > workings of a closed > assembly (Witango) - if something causes a problem (in this case, > compromising "state" > management), remove the element that causes the problem or don't use > the assembly. > > Make sure you understand "state" management before you try to > understand Witango (or any other > web platform) - in the meantime, don't use <@USERREFERENCEARGUMENT>. > > Its like I often say, the very first lesson in Web programming should > be about HTTP - if you > don't understand HTTP, then you shouldn't be allowed to code. > > "State" management is almost as important as HTTP, but "state" is > actually optional - whereas > HTTP is not. > > > > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
