Hello, all - I was doing some thinking today about the above three subjects. Now, I might sound like a complete tool here because I don't think I quite know exactly in which instances constructors and destructors can be used - but what about inside a session? Say I had a visitor hit a site. A session would start, and the constructor would preform some housekeeping with the session; setting data correctly, gathering other data, executing another PHP function, yada yada. Then, when the session expired, Mr. Destructor would come in and clean up - from within the session. Is this possible? Does it work this way? If so, or if not for that matter, please help me out here to better understand how these three elements interact with eachother, if at all. Also - how would one go about handling sessions behind a load-balancing configuration? The best I've thought of is to use some sort of load balancer which also has an NFS share. Sessions are created with this load balancer, and Apache or whatever proxy's the connection to the machines behind the load balancer. The machines behind the load balancer map the NFS share from the load balancer, and are able to interact with the session. I'm very curious as to how session tracking is done through multiple machines, as well. As always, thanks again for your time. -dant -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
