<quote who="justin randell"> > that really got me curious, so i had a poke around the 2.9.2 code base. > jeff, i'm wondering what led to a decision to reimplement php session > handling in custom code? seems the code that leads to pulling the $user > from a permanent store via an encrypted cookie value is exactly what > sessions are for? > > was it a desire to use a non-file based store and an aversion to using > custom session handlers? was it a desire to control the strength of the > cookie hash?
Most likely both... on top of that, consider WordPress's relative age, ease of installation / configuration (particularly on shared hosting platforms where the user has no control over the system), and desire to support older system components. An interesting question though, for which I'm sure there's more historical background (and rationale for not switching to PHP session handling in later versions)... I'll ask around and find out more. :-) - Jeff -- The Great Australian Internet Blackout http://www.internetblackout.com.au/ "Jane Austen is the Don Burke of romantic comedy." - Andrew Bennetts -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
