Musing to myself, I thought:

Apache and perl go together like hot cocoa and marshmallows.

With features like Cross-Language Remoting using mod_perlservice, we start to see a service-based framework emerge that will prove extremely useful to those who might need to write their client application in something other than perl.

Combine this with the use of Inline and its kin, and we begin to see a possibility for cross-language programming at the distributed application level, using perl as a core.

Personally, I like the idea of clients and servers being able to be written in the language of choice by their designers, all the while providing a stardard cross-language interface. It's not quite byte-code interlanguage calling and data sharing, vis. .NET, but it's a good strategy nonetheless. I believe that if logical interfaces are well-defined, then coding back from those interfaces should be possible in any language -- as long as there is some kind of glue to help things along.

I think that using Apache and mod_perlservice is a good start to one possible solution to the logical interface for a cross language framework.

Just a thought,
-v
"Perl. There is no substitute."

Replies are listed 'Best First'.
Re: An Emerging Cross Language Framework
by exussum0 (Vicar) on Nov 27, 2004 at 15:47 UTC
    SOAP and REST supposed to accomplish this ;)

    ----
    Then B.I. said, "Hov' remind yourself nobody built like you, you designed yourself"

Re: An Emerging Cross Language Framework
by samtregar (Abbot) on Nov 27, 2004 at 16:35 UTC
    I think that using Apache and mod_perlservice is a good start to one possible solution to the logical interface for a cross language framework.

    I think Apache/mod_perl and SOAP::Lite have already solved this. Why reinvent this wheel?

    -sam

      Why reinvent this wheel?

      Perhaps the effort is fueled by some rather clever fellow recently remarking that SOAP isn't a panacea. :)

        If so they must have misunderstood! Most of the problems I identified with SOAP are common to most RPC systems. Instead of just switching to another RPC system, Krang doesn't support RPC at all. Its XML system is based on TAR instead!

        It could be that mod_perlservice is a great advance over SOAP, but I've seen nothing so far to convince me. And nothing I've seen so far has convinced me that this new RPC system justifies a new mod_perl!

        -sam

        XML-RPC is good enough for most things that use SOAP, and it's faster and simpler and has less variants. YAML/RPC is what it's all about though :)