.net talking to ruby or perl

[Eps]

Hi there,

Is it possible to have .net application talk to and interact with a ruby
or perl application (either on the same machine or separate ones) ?.

Could Remoting/WCF be used to accomplish this or is the only option
something like xml-rpc (which i would guess would involve more overhead
than WCF).

In this scenerio assume that the .net app is the client and the
perl/ruby app is the server.

Thanks for your help.

 

[Mr. Arnold]

Hi there,

Is it possible to have .net application talk to and interact with a ruby
or perl application (either on the same machine or separate ones) ?.

Could Remoting/WCF be used to accomplish this or is the only option
something like xml-rpc (which i would guess would involve more overhead
than WCF).

In this scenerio assume that the .net app is the client and the perl/ruby
app is the server.

The perl application would need to be a XML Web service that the .Net
application would consume to pass data between the two solutions, either on
the same machine or seperate ones.

You can also use Perl.Net, which would be another type safe solution like C#
using the .Net Framework, where you could use .Net remoting I would assume.

http://www.dotnetpowered.com/languages.aspx
http://aspn.activestate.com/ASPN/NET/

 

[JDeats]

The leading contenders would be: XML-RPC, SOAP or REST. These are
standards that you can obtain code libraries for for Perl, RoR
and .NET/C#. They each have their strengths and they don't all behave
the same way, but they all let you talk to/interact with Ruby and Perl
as those languages have libraries to support these standards as well.
REST uses a different paradigm than XML-RPC/SOAP and may be more
appropriate, it just depends on what you're looking to accomplish.

WCF supports all of these standards. Do a web search for articles
comparing these technologies.

 

[Arne Vajhøj]

Is it possible to have .net application talk to and interact with a ruby
or perl application (either on the same machine or separate ones) ?.
Yes.

Could Remoting/WCF be used to accomplish this or is the only option
something like xml-rpc (which i would guess would involve more overhead
than WCF).

WCF is not a protocol - it is a framework that support multiple
protocols. I would expect SOAP to have bigger overhead than XML-RPC,
but some of the binary protocols less overhead.

SOAP is always an excellent choice when interoperability
across technologies is first priority.

In this scenerio assume that the .net app is the client and the
perl/ruby app is the server.

No difference.

Arne