[Fwd: Re: [PHP-DEV] PHP's vision]
| From: | Brian Foddy | Date: | Mon, 03 Jun 2002 16:59:16 +0000 |
| Subject: | [Fwd: Re: [PHP-DEV] PHP's vision] | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-84809@lists.php.net to get a copy of this message | ||
I admit I haven't been following this thread closely, but I agree and
don't think PHP should be trying to write a transaction system itself.
I do think it should try to interface with existing systems tho so
PHP can become the front-end for them.
I have a good start on a Tuxedo interface (php-tuxedo.sourceforge.net)
if you are interested.
Brian
Andi Gutmans wrote:
At 03:27 PM 6/3/2002 +0300, Jani Taskinen wrote:On Mon, 3 Jun 2002, Andi Gutmans wrote: the web but more for Enterprise transaction based applications such as billing systems.No I definitely don't. And in most cases I wouldn't use J2EE eitherfor suchTwisting your words a bit: You don't think PHP should be usedtasks ??but I'duse a C++ App server. There are also performance problems with J2EE App servers but often company's clients require J2EE.Most people I know who are working in these kind of demanding environments (soft real-time requirements) have written these themselves. I don't know of any open source ones except for ACE which isn't a complete app server but gives you a framework to start on. BEA's Tuxedo is a commercial example. AndiWould you write that C++ App server yourself or use some existing one? (just wondering whether there is some open source c++ app server around..)