LordHog@hotmail.com wrote:
> Hello,
>
> I was wondering what are the differences between using the
> System.Runtime.Remoting vs. System.Net.Sockets? I am sort of confused
> what the differences are between them and which particular framework is
> best suited for its own niche.
>
> I am planning on implementing some basic communications between a
> server that will run in the lab and from desktop machines that will be
> used for development/testing/integration activities. I would like
> client to query the server to see if anyone is currently using the
> facilities provided by the server and if no one is using the facilities
> provided that individual would have sole control until they logged out,
> but the server would also inform a client who has control. Some sort of
> basic items like that. What would be the better class framework to use,
> Remoting or Sockets? Thanks
>
> Mark

> I was wondering what are the differences between using the
> System.Runtime.Remoting vs. System.Net.Sockets? I am sort of confused
> what the differences are between them and which particular framework is
> best suited for its own niche.

<LordHog@hotmail.com> wrote in message
news:1154107951.129180.249020@m79g2000cwm.googlegroups.com...
> Hello,
>
> I was wondering what are the differences between using the
> System.Runtime.Remoting vs. System.Net.Sockets? I am sort of confused
> what the differences are between them and which particular framework is
> best suited for its own niche.
>
> I am planning on implementing some basic communications between a
> server that will run in the lab and from desktop machines that will be
> used for development/testing/integration activities. I would like
> client to query the server to see if anyone is currently using the
> facilities provided by the server and if no one is using the facilities
> provided that individual would have sole control until they logged out,
> but the server would also inform a client who has control. Some sort of
> basic items like that. What would be the better class framework to use,
> Remoting or Sockets? Thanks
>
> Mark
>

ThunderMusic wrote:
> I'd recommend sockets only if you need to, like if you need an extra
> performance boost or something like it... but if I stand with what you said
> you need I'd definitly go with remoting... Remoting is almost like having
> the power of your server on the local machine... Your objects will work
> almost like if they were local... you can call their methods, you can
> receive their events (you need to follow certain patterns, but you can do
> it), get or set their properties, et al. In your situation, Remoting is
> probably your best friend... ;) Beside, there is lots and lots of
> documentation on remoting out there : articles on internet, msdn, books, et
> al. It's a bit more complicated to find documentation for sockets in .NET
> and it would clearly be too much work for what you need...
>
> I hope it helps
>
> ThunderMusic
>
> <LordHog@hotmail.com> wrote in message
> news:1154107951.129180.249020@m79g2000cwm.googlegroups.com...
> > Hello,
> >
> > I was wondering what are the differences between using the
> > System.Runtime.Remoting vs. System.Net.Sockets? I am sort of confused
> > what the differences are between them and which particular framework is
> > best suited for its own niche.
> >
> > I am planning on implementing some basic communications between a
> > server that will run in the lab and from desktop machines that will be
> > used for development/testing/integration activities. I would like
> > client to query the server to see if anyone is currently using the
> > facilities provided by the server and if no one is using the facilities
> > provided that individual would have sole control until they logged out,
> > but the server would also inform a client who has control. Some sort of
> > basic items like that. What would be the better class framework to use,
> > Remoting or Sockets? Thanks
> >
> > Mark
> >