Re: Intercommunication control?
by "Jeffrey Tan[MSFT]" on 11/1/2007 3:48:00 AM
Hi Mojo,
You may take a start from the link below:
".NET Framework Remoting Overview"
http://msdn2.microsoft.com/en-us/library/kwdt6w2k.aspx
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Re: Intercommunication control?
by Tom Shelton on 10/31/2007 2:26:00 PM
On Oct 31, 8:04 pm, Spam Catcher <spamhoney...@rogers.com> wrote:
> Tom Shelton <tom_shel...@comcast.net> wrote innews:1193873411.358972.109790@i38g2000prf.googlegroups.com:
>
> > I wouldn't say that it is necessarily easier from a beginers
> > standpoint. I would say that simple socket communication is far
> > easier both from a programming and setup perspective....
>
> There's a lot of stuff the standard .NET socket libraries don't take into
> account, such as buffer overflows, errors during data transfer, sending
> large amount of data, etc etc. There's just too many small details for a
> beginner to worry about.
>
> > That said, I agree that often wcf/remoting is probably the best
> > answer.
>
> I wrote a socket server which handles >150 simultaneous call center
> clients... I swore to myself I'll never do that again ;-)
I am very aware of what .NET sockets are and what they aren't. I've
done lots of work with them - everything from writing my own
webserver, email clients, and news readers. Not to mention, a
predictive dialer system that integrated with a legacy system via a
tcp/ip server that handled probably double 150+ connections and a
service to pull data off of an sql database for clients running on a
Unix environment.... Yes, there are details you have to deal with when
doing more complex stuff - but, it sure sounds to me that the OP isn't
dealing with complex stuff.
Still - I agree that in his case, wcf/remoting is probably a better
answer. But, I don't necessarily agree that remoting is simpler, it
has it's details to work through as well. Like the differences
between client and server activated objects? What is a singleton?
What protocol should be used for serialization? etc, etc. Anway, I
don't want to get into an argument. The OP asked about tcp/ip
controls - so I answered that. You added the thought to use
remoting. I think the OP has enought information now to make an
informed decision :)
--
Tom Shelton