Client - server communication

[Christian Westerlund]

Hi!

Does anyone know if it is possible for a client server communication
easy in .NET with these requirements:

The client always initiates the communication
The server only answers (responds)
Uses port 80, skips firewall
The server computer doesn't have a IIS or web server

I have thought about remoting but it feels a little bit over the top, we
are only sending information to the client .

/Christian

[Arran Pearce]

Remoting is a good answer. Use the Http Channel. Very easy to code,
only about 5 lines on client and server.

Another option is to use System.IO and setup some UDP or TCP sockets.
This is also quite easy.

If you need some code examples mail me.

Christian Westerlund wrote:

Hi!

Does anyone know if it is possible for a client server communication
easy in .NET with these requirements:

The client always initiates the communication
The server only answers (responds)
Uses port 80, skips firewall
The server computer doesn't have a IIS or web server

I have thought about remoting but it feels a little bit over the top, we
are only sending information to the client .

/Christian

[Elp]

"Arran Pearce" <arranpearce@NO _SPAMcellhire.c om> wrote in message
news:uv******** *****@tk2msftng p13.phx.gbl...

Remoting is a good answer. Use the Http Channel. Very easy to code,
only about 5 lines on client and server.

Another option is to use System.IO and setup some UDP or TCP sockets.
This is also quite easy.

And another option would be to use a Web Service with WSE 2.0 (now in
release version) which allows to host a Web Service within a Windows
executable without the need of a Web Server.Here is a link to a good article
that explains that, unfortunately in French:
http://www.c2i.fr/code.aspx?IDCode=576
You can find information in English here:
http://msdn.microsoft.com/webservices/building/wse/ (the feature i'm talking
about is Web Service Messaging)

I guess however that the Remoting way with HTTP channel would be much easier
and more powerfull although not interroperable (but i'm not sure if WSE 2 is
that much interroperable either)

[Christian Westerlund]

Hi Elp!

Thanks for the tip, I'll look into that!

/Christian

Elp wrote:

"Arran Pearce" <arranpearce@NO _SPAMcellhire.c om> wrote in message
news:uv******** *****@tk2msftng p13.phx.gbl...

Remoting is a good answer. Use the Http Channel. Very easy to code,
only about 5 lines on client and server.

Another option is to use System.IO and setup some UDP or TCP sockets.
This is also quite easy.

And another option would be to use a Web Service with WSE 2.0 (now in
release version) which allows to host a Web Service within a Windows
executable without the need of a Web Server.Here is a link to a good article
that explains that, unfortunately in French:
http://www.c2i.fr/code.aspx?IDCode=576
You can find information in English here:
http://msdn.microsoft.com/webservices/building/wse/ (the feature i'm talking
about is Web Service Messaging)

I guess however that the Remoting way with HTTP channel would be much easier
and more powerfull although not interroperable (but i'm not sure if WSE 2 is
that much interroperable either)

[Arran Pearce]

On the server is call:
HttpChannel chan = new HttpChannel(454 4);
ChannelServices .RegisterChanne l(chan);

Type myObjectType = typeof(myObject );

RemotingConfigu ration.Register WellKnownServic eType(myObjectT ype,"EndPointNa me",
WellKnownObject Mode.SingleCall );

and on the Client Call:

HttpChannel chan = new HttpChannel(0);
ChannelServices .RegisterChanne l(chan);
myObjectInterfa ce r =
(myObjectInterf ace)RemotingSer vices.Connect(t ypeof(myObjectI nterface),"http ://localhost:4544/EndPointName");
My Client app has a Class which is the interface of the object i am
sharing and the server app has the full object class.
I normally have the client using a interface rather than the full class
so if i change the internals of the class then i dont need to
redistribute the client.
Beeeeeeeeeeeeve s wrote:

Wouldn't mind seeing some of your examples of using remoting to do simple communication between client and server if you have any.

Also would be interested in seeing ones of a service communicating with a front end app on the same machine.

mail me to benjtaylor at hotpop dot com if you have any good examples

"Arran Pearce" wrote:

Remoting is a good answer. Use the Http Channel. Very easy to code,
only about 5 lines on client and server.

Another option is to use System.IO and setup some UDP or TCP sockets.
This is also quite easy.

If you need some code examples mail me.

Christian Westerlund wrote:

Hi!

Does anyone know if it is possible for a client server communication
easy in .NET with these requirements:

The client always initiates the communication
The server only answers (responds)
Uses port 80, skips firewall
The server computer doesn't have a IIS or web server

I have thought about remoting but it feels a little bit over the top, we
are only sending information to the client .

/Christian