Re: Re: cvs: php4 / TODO

Quoting Sebastian Bergmann <sb@phpopentracker.de>: > - Distributed Applications SOAP support seems like a good start for this; I believe we already have xml-rpc, right? Also, the corba client support (satellite extension) is a good start for the client end; letting php be the server side would be another step. > - permanentely running PHP Application, that's not (entirely) > http-request driven Sounds like something that you could do with the php cgi (command line version), disabling max_execution_time, and an event loop, though maybe additional capabilities are needed as well. > This was what I mentioned in a talk at the congress, I was told that Java > application servers provide more sophisticated means for this. Things like fail-over, etc? It'd be good to get an idea of how this could work at the app level - I'm not really sure what java app servers provide, so I'm asking... > Just to make myself clear, the purpose of my mail was not to blame someone > or to criticize PHP. PHP does currently work very good and is perfectly > suited for low to middle complex / trafficked sites and web applications. Of course! I'm just trying to do a little bit of devil's advocate, and also get down into some concrete ideas of what we really need to meet these goals. > _But_ what are the dreams / plans / visions for the future of PHP so that > this state of "excellence" persists? Where will PHP stand in two years from > now? Will it then still be the best choice? Will it become even better and > take over the lead in the market of web development platforms? I recall Zeev at one point stating that the php3 scripting engine was such a major upgrade from the php2 state of things that he couldn't see the need for a major rewrite anytime soon. But then he and Andi went and wrote Zend and php4. So I'm not sure it's a question that anyone can accurately answer. Not that it isn't worth thinking about. :) -chuck -- Charles Hagenbuch, <chuck@horde.org> must... find... acorns... *thud*