Eric Butera schreef: > On Thu, Nov 20, 2008 at 8:37 AM, Yeti <yeti@xxxxxxxxxx> wrote: ... >> > > Autoload. Why on earth would you do such a thing? autoload ... your neighbourhood opcode cache performance killer, then again so is file based sessions (for ease of use I stick my session files on /dev/shm/foo [i.e. RAM] if/when using a file based session handler ... I figure if the box goes down and takes /dev/shm with it the lost session data is the least of my worries ... besides by the time the box is up current visitors will generally have given up and left already) ... and storing a path to a file containing a serialized object in the session is a bit nuts, you might as well store the serialized object in the session and save at least one file write/read. storing a serialized object, as opposed to letting the session handler do transparent serialization can help you get round an infrastructure problem (where you can't load the class before starting the session) and also can improve performance where you might not want/need to initialize the given object on every request. > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
