Re: Sessions and Objects

> Pfft. You just lost a lot of respect with that post. > PHP has a problem. You are saying that "Hey, I > don't have a need for it." Wrong. You have a very > vested interest in the life and death of PHP as you're > doing a whole lot of consulting these days. PHP has > a serious problem, and it's causing a lot of users to > lose a lot of time and patience. Would you prefer that > everyone who needs session objects move away from PHP? > If the answer is no, then perhaps you should consider fixing > PHP or your consulting business will dry up right fast - or at > least take a dive since PHP will be deemed unusable in > a session-requiring application. Once it becomes common > knowledge, so will your book-writing career (at least for PHP.) I don't make money consulting, and I certainly don't make any money writing books. PHP is a community project. It is not my project, nor is it even the development team's project. It is our project. You can't pressure people into fixing stuff just because you really need it fixed. If you don't have the ability to help fix a problem, you can contribute by identifying it, which you have done. Thank you for that. But attacking the developers in different ways is not going to make anybody any more motivated to fix anything for you. There are lots of bugs still to be fixed. Document the bug properly, add it to the bugs database, and if you look at the bug stats you will find that you stand a decent chance of having it fixed within a couple of weeks if you don't piss too many people off along the way. You did submit this to the bugs database, right? > It's all about doing what you want, going from point a to point b > in a rapid fashion without sacrificing performance, scalability, > or hassle. If PHP cannot do that, perhaps I need to take some > time and evaluate other tech. > > Or perhaps you're right and I need to contribute. Working two jobs > (only one of which is PHP) and trying to prep for my wedding > leaves me PLENTY of time to fix your (PHP dev group's) bugs, right? No, they are your bugs too. We are all busy people. > I'll look at it tonight, or so. If you (PHP group) did your jobs correctly > then the fix should be minor. If not, then I'm unwilling to proceed from > here without some compensation. It's only fair, right? None of us are > in the charity-consulting business, after all.... You are not the first, and certainly not the last person to come along with this sort of attitude. Demanding a fix and threatening to choose another technology if your problem is not fixed. All open source developers have to deal with this attitude and we are getting used to it. Sometimes I deal with it better than other times. But every now and then it just gets to one of us. We are talking about a 4.0.0 version here. The session code is all new, and yes, chances are there are a few bugs in it. Chances all also pretty good that they will get fixed. The fact that nobody replied to your various posts about a bug is just an indication that people are too damned busy fixing stuff and working on other things. Bugs in the bug database are getting fixed at a good rate. The list of fixes in 4.0.1 is impressive. Heck, your problem may even already be fixed. Did you check? -Rasmus