[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.sdk

RPC Java/.NET

Lloyd Dupont

1/14/2003 1:43:00 AM

Hi,

I have a "multilanguage" application. I have a Java application. Really
java, compiled with javac and run with Sun's JVM (NOT J#).
And I also have a .NET application (write in C#)

Problem: I want all of them to communicate, if possible with a high level
protocol (like RMI or Remoting)

I found XML RPC, but it needs a WebServer.
I know about Corba, but you need an ORB and, beside, it has always seems
awfully complicated to me.

Does any of you have an other idea ?
12 Answers

Ajay K. Agrawal

1/14/2003 2:05:00 AM

0

You can use sockets.

-Ajay

"Lloyd Dupont" <lloyd@galador.net> wrote in message
news:uY0iSW2uCHA.1628@TK2MSFTNGP10...
Hi,

I have a "multilanguage" application. I have a Java application. Really
java, compiled with javac and run with Sun's JVM (NOT J#).
And I also have a .NET application (write in C#)

Problem: I want all of them to communicate, if possible with a high level
protocol (like RMI or Remoting)

I found XML RPC, but it needs a WebServer.
I know about Corba, but you need an ORB and, beside, it has always seems
awfully complicated to me.

Does any of you have an other idea ?

Lloyd Dupont

1/14/2003 2:18:00 AM

0

oh dear...
I explain you, a 'high level communication protocol' obviously use socket.
but it authorise you to write simple method call. All networking code being
hide/implemente in the RPC tool/API.....
do you dare compare Socket to Remoting ?
of course Remoting use socket, of course, but it had much more value....

Anyway, after further reading it seems that XML-RPC (http://www....)
could be used as standalone application....

"Ajay K. Agrawal" <ajaykagrawal@hotmail.com> wrote in message
news:#EjZwj2uCHA.2668@TK2MSFTNGP12...
> You can use sockets.
>
> -Ajay
>
> "Lloyd Dupont" <lloyd@galador.net> wrote in message
> news:uY0iSW2uCHA.1628@TK2MSFTNGP10...
> Hi,
>
> I have a "multilanguage" application. I have a Java application. Really
> java, compiled with javac and run with Sun's JVM (NOT J#).
> And I also have a .NET application (write in C#)
>
> Problem: I want all of them to communicate, if possible with a high level
> protocol (like RMI or Remoting)
>
> I found XML RPC, but it needs a WebServer.
> I know about Corba, but you need an ORB and, beside, it has always seems
> awfully complicated to me.
>
> Does any of you have an other idea ?
>
>
>

Nick Wienholt

1/14/2003 2:23:00 AM

0

Why not use SOAP? .NET has great support, and most modern Java libraries do
too.

Nick Wienholt, MVP
Sydney Deep .NET User Group www.sdnug.org

"Lloyd Dupont" <lloyd@galador.net> wrote in message
news:uY0iSW2uCHA.1628@TK2MSFTNGP10...
> Hi,
>
> I have a "multilanguage" application. I have a Java application. Really
> java, compiled with javac and run with Sun's JVM (NOT J#).
> And I also have a .NET application (write in C#)
>
> Problem: I want all of them to communicate, if possible with a high level
> protocol (like RMI or Remoting)
>
> I found XML RPC, but it needs a WebServer.
> I know about Corba, but you need an ORB and, beside, it has always seems
> awfully complicated to me.
>
> Does any of you have an other idea ?
>
>

Lloyd Dupont

1/14/2003 3:53:00 AM

0

hu ? why not ...
without looking like a dummy I want something simple which spare me anywork.

I want someting where I don't care about underlying protocol, except they
communicate together.

So far I'm confident that .NET could speak with itself using SOAP or some
others protocol. But I dont know about Java.
Whereas if you ever go there:
http://www.... you will see that many language (I target Java,
ObjectiveC & C#) have a 'XML RPC package' were you don't care about
underlying protocol (actually XML) it just interoperate with a few line of
code.
Cool, it's what I was looking for.

But, however, I'm curious, could you point me out some link where I would
find resource/tutorial/howto make 2 application spoke together (high level
communcation=> method call), (without a WebServer, if possible), in a few
line.
And with dev kit for .NET/Java/Objective-C (C would be ok instead of
ObjectiveC)

Nick Wienholt

1/14/2003 4:38:00 AM

0

> But, however, I'm curious, could you point me out some link where I would
> find resource/tutorial/howto make 2 application spoke together (high level
> communcation=> method call), (without a WebServer, if possible), in a few
> line.
> And with dev kit for .NET/Java/Objective-C (C would be ok instead of
> ObjectiveC)

SOAP support in .NET uses zero lines of code - you simply add a web service
reference, and program against the reference like a normal object. See
other vendors websites for their SOAP offerings. A quick look at the
http://ja... shows SOAP featured in the first article listed on the
Java homepage.

SOAP doesn't mandate the use of a web server - you simply need an
application listening on a particular port for SOAP requests. A web server
generally makes this easier, but you could write a custom Windows Service to
do it too.


Nick Wienholt, MVP
Sydney Deep .NET User Group www.sdnug.org

Lloyd Dupont

1/14/2003 4:47:00 AM

0

mmhh...
you're right....
I stop playing the dummy and look at that.
Thanks for your patient reminders.

> SOAP support in .NET uses zero lines of code - you simply add a web
service
> reference, and program against the reference like a normal object. See
> other vendors websites for their SOAP offerings. A quick look at the
> http://ja... shows SOAP featured in the first article listed on the
> Java homepage.
>
> SOAP doesn't mandate the use of a web server - you simply need an
> application listening on a particular port for SOAP requests. A web
server
> generally makes this easier, but you could write a custom Windows Service
to
> do it too.
>
>
> Nick Wienholt, MVP
> Sydney Deep .NET User Group www.sdnug.org
>
>
>

Jon Davis

1/14/2003 5:45:00 AM

0

> SOAP doesn't mandate the use of a web server - you simply need an
> application listening on a particular port for SOAP requests. A web
server
> generally makes this easier, but you could write a custom Windows Service
to
> do it too.

Any service running on port 80 that handles HTTP requests is considered a
web server. You don't necessarily need a full-blown
_web_application_server_, but it's pretty difficult to implement a SOAP
listener without one.

Jon

Jon Davis

1/14/2003 5:48:00 AM

0

hmm I suppose there might be SOAP listener classes in the .NET framework
that facilitate the HTTP request/response handling without the use of IIS?

Jon


"Jon Davis" <jon@REMOVE.ME.PLEASE.jondavis.net> wrote in message
news:ulNB2f4uCHA.2544@TK2MSFTNGP11...
> > SOAP doesn't mandate the use of a web server - you simply need an
> > application listening on a particular port for SOAP requests. A web
> server
> > generally makes this easier, but you could write a custom Windows
Service
> to
> > do it too.
>
> Any service running on port 80 that handles HTTP requests is considered a
> web server. You don't necessarily need a full-blown
> _web_application_server_, but it's pretty difficult to implement a SOAP
> listener without one.
>
> Jon
>
>

Nick Wienholt

1/14/2003 5:56:00 AM

0

> hmm I suppose there might be SOAP listener classes in the .NET framework
> that facilitate the HTTP request/response handling without the use of IIS?

Yep - the remoting infrastructure, and the HttpServerChannel in particular.

Nick Wienholt, MVP
Sydney Deep .NET User Group www.sdnug.org

Jon Davis

1/14/2003 6:02:00 AM

0

cool

"Nick Wienholt" <goyousharks@hotmail.com> wrote in message
news:OcyNcl4uCHA.2448@TK2MSFTNGP11...
> > hmm I suppose there might be SOAP listener classes in the .NET framework
> > that facilitate the HTTP request/response handling without the use of
IIS?
>
> Yep - the remoting infrastructure, and the HttpServerChannel in
particular.
>
> Nick Wienholt, MVP
> Sydney Deep .NET User Group www.sdnug.org
>
>