Re: Sessions and Objects

> Apologies are in order. I guess I've been working far too long in > "commercial" code, and my attitude was off-base. You are correct in > the fact that it IS OSS, and I thought that PHP was yours/Zend's. In > one of your talks you spoke like Zend all but owned PHP, and thus > they (and you) would have more of an investment/gain from it. If not, > my apologies. Again, I'm too used to someone "owning" software > and being responsible for it's care/feeding/growth. No worries. I am curious, which talk was this? I can't imagine saying something that would give this impression as I have absolutely no involvement with Zend Technologies. I don't work for them nor do I own any stock in the company. I think Zend Technologies is a good thing in that it has given a number of people the opportunity to work fulltime on PHP related things and draw a pay cheque from it. Perhaps I said something to this effect and gave the impression that I was one of these people getting paid by Zend. That is not the case. > Would everyone rather see > 1) No autoloading of classes. You call $php_var = php_load_class("class_name"); > 2) Autoloading of classes with the same name? ie, if you register your class as > "foo" then you'll always have "foo" available (including methods). > > Option #1 I put up there simply because if you have (somewhere) 100 classes > registered to the session but you're not using 99 of them then you keep > speed up instead of calling the create/destroy/load methods for the > unused 99 - you only load what you need. > This is my preference, but there's a lot of people out there and maybe > someone has a better idea that won't break existing sites... I think both options could be implemented. This stuff is more in Sascha and Andrei's domains that mine though. -Rasmus