EMAIL PROTECTED]
Subject: mod_perlservice? Heck Yeah!
Gentlemen,
mod_perlservice rocks. I know because I wrote it.
Let my email explain why I wrote mod_perlservice and why it will provide
obvious benefits to webservices developers.
Why not just use XML-RPC?
XML-RPC is a standalone system (excep
On Fri, 2004-11-26 at 18:57 -0500, [EMAIL PROTECTED] wrote:
> On the other hand I understand the emotion. You may have felt threatened
> by a new embedded perl system on Apache. I hope I have allayed your fears
> since mod_perlservice doesn't threaten your work, but instead complements
> it.
After
I think it's great that you are proud of your work. Criticism will make
your work better.
Calling this "cross-language remoting" is kind of a misnomer, because
standards like SOAP/XML-RPC are what allow RPC to occur cross-language.
Yours is a Perl server solution (by definition), and not bas
On Fri, 26 Nov 2004 [EMAIL PROTECTED] wrote:
> XML-RPC is a standalone system (except for the Java-Apache extension). If
> you need to run your webservices system on port 80, for firewalling issues
> for instance, you can't also run Apache. That's not ideal. With
> mod_perlservice, you can host RP
All I ask is that you kill that center tag on your site :)
I have an aborted project that had been intended to use XML-RPC with PHP
being the client, and mod_perl being the server. I am interested in what
you are doing, but I am wondering how much use it is for this kind of
project if it is not
Gentlemen,
mod_perlservice rocks. I know because I wrote it.
Let my email explain why I wrote mod_perlservice and why it will provide
obvious benefits to webservices developers.
Why not just use XML-RPC?
XML-RPC is a standalone system (except for the Java-Apache extension). If
you need to run y
