Hi there going back to the discussions of objects in a session. I would like to know what are the benifits of this, and in what scenarios would it be used. I have an application I am trying to make scalable if possible, it uses a sub class to a phplayers menu class which parses an xml file and generates the menu depending on certain attributes like access for instance. It will check if the user is an admin or normal user and not show it. Would this one be useful for adding into a session across pages ? Also i have a date/calender class which is used across pages, it dynamically generates list menus of day/month/year , somehow it slows down the page when loading, would it be useful to go into a session aswell ? I dont want to overdo the session vars aswell.
Sounds like you should put those in a session, yes. If you put the vars in your session, you'll be storing them in the filesystem as serialized variables, but it's better than doing lots of querying / XML processing / etc. If you're worries about the filesystem, you could also use a RAMDrive for your session storage.
-- paperCrane <Justin Patrin>
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
