Please advice technology

[=?Utf-8?B?SmVzcGVyLCBEZW5tYXJr?=]

Hi
I would like to write 2 applications. 1st app sends arguments across network
to 2nd app that returns a result, just as you would if it was within same
application.
The argument sent could be some kind of struct e.g.

What technology should I learn/ apply for being able to do this? SOAP?

regards
JEsper

[Alberto Poblacion]

"Jesper, Denmark" <Je***********@discussions.microsoft.comwrote in message
news:29**********************************@microsof t.com...

I would like to write 2 applications. 1st app sends arguments across
network
to 2nd app that returns a result, just as you would if it was within same
application.
The argument sent could be some kind of struct e.g.

What technology should I learn/ apply for being able to do this? SOAP?

Since you are asking in a .Net programming group, I assume that you have
..Net on both ends. You may wish to use Windows Communication Foundation
(WCF) which will let you select various communication options (including
SOAP) from a single source code by means of configuration files.

[Alcides]

On Jun 30, 9:16*am, Jesper, Denmark
<[e-mail]:

Hi
I would like to write 2 applications. 1st app sends arguments across network
to 2nd app that returns a result, just as you would if it was within same
application.
The argument sent could be some kind of struct e.g.

What technology should I learn/ apply for being able to do this? SOAP?

regards
JEsper

I think you can use web services in this case...

Alcides.
http://alsql.blogspot.com.

[=?UTF-8?B?QXJuZSBWYWpow7hq?=]

Jesper wrote:

I would like to write 2 applications. 1st app sends arguments across network
to 2nd app that returns a result, just as you would if it was within same
application.
The argument sent could be some kind of struct e.g.

What technology should I learn/ apply for being able to do this? SOAP?

If both ends are in .NET and you expect them to stay that way, then
remoting is more efficient than SOAP/HTTP.

(or WCF with endpoint binding="netTcpBinding" and
binding="NetNamedPipeBinding" which I think is doing
approx. the same)

Arne