Remoting and net.sockets

[Guest]

I have a question as to when remoting should be used as opposed to net.sockets.

 

[Mohamoss]

hi

i would say use sokets and not remoting if you will send small volume of
data, and go for remoting while sending large objects of data. remoting
give you many nice features( like using IIS security with http channals).
sockets would allow you to get to a lower level but from my experience,
remoting performance is much faster
Mohamed Mahfouz
MEA Developer Support Center
ITworx on behalf of Microsoft EMEA GTSC

 

[Roy Fine]

I have a question as to when remoting should be used as opposed to

net.sockets.

That is a rather broad question - and I'm sure you get a flood of responses
touting first one, then the other. Don't expect to get the *right* answer,
because the right answer will depend almost entirely on design requirements.
I suggest that you get a good book on .NET remoting.

Remoting allows you to create an object on a "remote" system, and call
methods on that object. The method calls could be to fetch data and return
to caller, but often the calls are to do processing on the remote machine
that either could not or should not be handled on the caller/client
machines. Remoting provides RPC/DCOM functionality to the managed .NET
application.

sockets allows you to send packets of data from one endpoint to another.
For large amounts of data, sockets may provide a performance advantage.

regards
roy fine

 

[Kiran]

Well... I would go for Sockets if I want to send small amount of data
frequently else I'll stick to Remoting. Remoting takes a lot of time to
Serialize and DeSerialize for frequent small burst of data transfer.

Regards
Kiran

I have a question as to when remoting should be used as opposed to

net.sockets.