After reading some articles I have new question about .NET remoting.

What to use: sockets or .NET remoting and pass object with values and methods to clients?

If I use sockets, everythink is clear - server/client comunicates by sending binary data, that can be serialyzed object or just a simple command with few parameters. In this way I need to read more about asyncronous call to send commands to all clients the same time and not wait while previous command to complete.

If with .NET remoting, I need to understand few things more.
Etc. there is class with fields and methods created in server. After client connects, it asks for this object by reference. He gets the same object as in server (etc. orders list) Then, if any client change any of the fields, such object is changed to all of others clients? If yes, it's simpler, becouse I do not need worry about sending data, accepting some commands and I just code one class with fields and methods. If this is the method how .NET remoting is working over TCP using binary may it run using HTTP? I know, that HTTPis stateless, but I found on MSDN that .NET Remoting can be used over HTTPeven with callbacks? What this means? Does his mean that if client changes the object, server is notified, but if server changes the object client isn't notified, becouse of how HTTPworks (request/response)?



Thank you in regards.