On 8 Jul 2001 [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
> > * Sean R. Bright wrote:
> >> I am not bringing this up for discussion as I know alot of the group is
> >> against it, I am just wondering if anyone would be interested in a seperate
> >> project to get PHP to run as an Application Server.
> >
> > [1]: first step IMHO would be definining "PHP AppServer",
> > e.g. what features (crypting data between AppServer and
> > web server and so on) are necessary and how other languages
> > (Java, Zope, ...) define their "AppServer".
>
> you could create this "application server" and define a new protocol
> for transferring the information, etc.
>
> or you could just use http (with ssl?) and apache as a backend
> "application server" with almost any web server on the front-end.
> (mod_backend for apache is a particularly good way to handle coupling
> multiple frontends to multiple "application servers".)
>
> sure, it isn't necessarily buzzword-compliant, but it already exists,
> and uses proven protocols and tools.
actually http is a bad choice for communicating with an application
server. maintaining state, bundling calls and all that is hackery at
best with http, there must be a better standard (is bxxp still vapor?)
xml-rpc and soap add too much overhead to be used at such a level
imho, and they're both currently based on http. there's corba, but then
there's all this drudgery with choosing an orb etc, plus it's not exactly
lightweight. hm, i feel a custom utf8-based text protocol coming :)
- Stig
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
