One problem you run into with this kind of project is making the project be a "BE-ALL-END-ALL" to every problem. (Kind of recursive, eh)
> - clustering, > - management of server farms, > - transparent fail-over, > - load balancing > - application deployment without restarting server > - advanced queueing > - database connection pooling These items depend totally on your environment you run PHP in. In Linux you could use, possibly: * Clustering - Beowulf * Management - WebAdmin? * Transparent - Depends on your implementation and Database systems * Load Balancing - Beowulf? Kernel level NAT? * App Deploy - PHP already does this * Advanced Queuing - Depends on you Web Server. Apache is getting better at this with 2.0 I think. * Database Connection Pooling - Already handled in PHP with pconnect? One area where ASP and MS have a problem is trying to put everything inside the specific language, instead of having several projects that happen to work together. This is where UNIX/Linux shines, I believe, and it has been working well for PHP as well. Making PHP work a certain way because a specific platform doesn't have the different items should not be a deciding factor. Nor should putting the stuff in PHP because the different platforms have different means of making the stuff happen. In essance PHP would become it's own Web Server, which would bring about a whole new level of potential issues. Not to mention time frame to get it implemented. -- Scott Carr OpenOffice.org Whiteboard-Doc Maintainer http://whiteboard.openoffice.org/doc/ Quoting John Lim <[EMAIL PROTECTED]>: > > "Jani Taskinen" <[EMAIL PROTECTED]> wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > On Sun, 2 Jun 2002, Sebastian Bergmann wrote: > > > > So what really ARE the needs of more advanced developers? > > (I'm starting to sound like a broken record now :) > > > > --Jani > > > > > Hi, > > I like the PHP language the way it is with some exceptions. Private > members > and methods are essential from a security view-point, and perhaps > application variables, but that's about it. My main problem with PHP's > direction is that it seems stuck at the low-end of the corporate world. > > Let me explain. I'm developing extranets with PHP and occasionally I get a > checklist of required features from a customer. Features such as: > > - clustering, > - management of server farms, > - transparent fail-over, > - load balancing > - application deployment without restarting server > - advanced queueing > - database connection pooling > > I believe that many of these features should probably not be part of the > language, or are already available as separate libraries or can be > implemented without modifying PHP, as Smarty has proved with templates. > However there is no one central resource that explains where you can find > the knowledge or source code to implement this. Is there any company > addressing all these issues. Let me know! > > For example, one spec I had to comply for a recent proposal was - NO SINGLE > POINT OF FAILURE. I looked at msession and I asked myself, does it provide > support for a backup session server on failover? Reading the docs, I think > not. Of course a database-backed session handler can provide failover > support, but where can I get proven tested code that I know is reliable > without having to write it myself? > > Does this mean that when i become more successful and get larger clients > with Enterprise requirements I have to abandon PHP and switch to Java or > MS.NET? I hope not. > > Regards, John > > > > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
