PHP 4 has a transparent session options that will automatically look for any relative links and add a session param to the URL. But this can have unpredicatble effects w/ certain javascript routines (and then you'd have a world of work to rewrite each page to handles sessions differently)
There is also a constant SID that is always available that has the seesion id in URL friendly form. <A HREF="nextpage.php?<?=SID?>"> Other good ideas are session.name = The name of the seession cookie or param (default = PHPSESSID) and session_id is the session vairable. http://www.php.net/manual/en/ref.session.php I like the way they do it its very clear and easy to override the key params (such as the session domain) and you can easily turn sessions off in pages that do not need them (although if you do not have cookies then each page would need session support) -Aaron ----- Original Message ----- From: "Mike Orr" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 01, 2001 12:58 AM Subject: Re: [Webware-discuss] Europe Goes After the Cookie > On Wed, Oct 31, 2001 at 05:58:34PM -0800, Tavis Rudd wrote: > > On Wednesday 31 October 2001 16:43, Chuck Esterbrook wrote: > > > At 05:48 PM 10/31/2001 +0000, [EMAIL PROTECTED] wrote: > > > >Did anyone get anywhere in implementing non-cookie identification > > > >mechanisms in Webware? ;-) > > > > What are the options? How does PHP implement 'transparent session > > handling'? > > 1) Session ID in a cookie. > 2) Session ID in a GET parameter. > 3) Session ID in a hidden form field. > 4) Session ID in a path component (superdirectory). > > PHP itself doesn't provide sessions. PHPLib (a third-party set of > classes) does. It automatically switches between (1) and (2) whenever > you turn cookies on and off. > > However, getting your application to support (2) is a huge pain. > We did it for one site but skipped it for the latest site. You can't > just hardcode URLs in your pages. Instead, every URL has to go through > a function that appends the session ID if necessary. This means using > a template variable for every single URL, even when you wouldn't > normally. Don't forget FORM ACTIONs. > > (4) is quite intriguing and may end up being the way of the future. > It was recently added to Webware, and there are proposals pending > to allow multiple CGI variables to be encoded this way. > > -- > -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] > https://lists.sourceforge.net/lists/listinfo/webware-discuss _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
