Musing to myself, I thought:
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,In reply to An Emerging Cross Language Framework by Velaki
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |