Remoting and Messaging

[Dennis Owens]

I want to develop a Client/Server messaging system that
does not require Microsoft messaging. I want to use
the .Net remoting, but I am having some real problems with
the remoting. The remoting really seems to be a one way
street in terms of messaging. Ex.( The Client can
communicate with the server and get information back from
the server, but the server cannot make a call to the
client unless you set up another remoting session were the
rolls are reversed) Any way the real question is, should I
be using Remoting for a simple light weight messaging
system? I do not want to use Microsoft Messaging.

Thanks
Dennis Owens
(e-mail address removed)

 

[Guest]

-----Original Message-----
Dennis:

It really depends on what you are trying to do. For instance, you may not
need to use either methodology. If you are simply pushing data back and
forth, you can use simple sockets programming, a web service(s) just to
name two.
MessageQueues do very well in this environment but you sound resolute in
that you do want to use them.

Let me know what you are trying to do and hopefully I can be of more help.

Bill



.

We are developing an application that will some day run on
anything from a computer down to a PDA ( this is were the
light weight comes in). The messaging that we want to send
will be very sraight forward. If one of the clients has
changed some data, the other clients need to know about
it. If the clients are not on line then the message may
have to wait until they are on line. The messages
themselves right now are simple event codes, but that may
change and we may need to send objects in the future. My
biggest problem with Remoting right now is that the client
and the server both need to be able start a message. I
would prefer to use sockets but the development team is
against it right now, and I am looking for more options.
So I hoped this answered some questions.