in reply to Integrating Perl into language independent networked applications

Use Apache. Everyone knows how to craft an HTML request. Everyone knows how to read an HTML response. You can even have the responses be XML, binary ... whatever.

Plus, Apache allows you to use create your own HTTP commands. So, if you don't like GET, POST, and HEAD, you can add FOO and BAR. (There's an example in the Apache2 docs for adding EMAIL.) So, you can craft your own language of HTTP messages.

Oh - avoid Tuxedo. It sucks rocks ... and does that badly, too.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

  • Comment on Re: Integrating Perl into language independent networked applications

In Section Seekers of Perl Wisdom