On Fri, Jun 22, 2001 at 08:32:45AM -0000, [EMAIL PROTECTED] wrote: > > operation without cookies (hooks are provided, but it's "do it > >yourself"), > > automatic switching between cookie and cookieless operation > > Actually, thinking about it, I would almost expect it to be hook-in > functionality. Whilst there probably do exist ways of suggesting (or > "renaming") the URL that a client has just accessed, overriding the URL > supplied by the client whilst not redirecting the client, it has never been > desirable functionality on my part. Not sure what you mean here, but one issue I forgot to mention is that if you're going to do cookieless sessions, you have to put the session ID into *every internal link* on a page. Thus, you can't just use static links, you have to make every one of them a plug-in variable and call the method that sessionizes the URI. This can be quite an inconvenience. It sounds like your application may be different than general session management. You just want to maintain the state between the form pages, rather than across the entire site? Then automatic hidden fields on forms may work for you. But if you want to allow the user to go to a non-form page and back, while still maintaining the form values, you'd need a traditional session object. Otherwise you'd force the entire site to build every page in the forms framework. > >On Thu, Jun 21, 2001 at 02:51:19PM -0000, [EMAIL PROTECTED] wrote: > >> I see one advantage of this system being the avoidance of any need to store > >> session information on the server, and to be obliged to implement session > >> timeouts - I hate visiting Web sites where my session expires after five > >> minutes just because I had to respond to an e-mail. > > > >Then set the timeout to half an hour, three hours or ten hours. > > Can I control cookies sent to me in this way? I never looked at cookie > management seriously in browsers, but then isn't the session "garbage > collection" that one often experiences something that the application itself is > imposing on the server side, and that it is most likely discarding my session's > state (or data) at such frequent intervals? Expiring session data happens on the server, so you have no control over it. I was talking about lengthening the timeout on your sites, so that your visitors wouldn't get caught in that trap. -- -Mike (Iron) Orr, [EMAIL PROTECTED] (if mail problems: [EMAIL PROTECTED]) http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/webware-discuss
