By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,651 Members | 1,908 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,651 IT Pros & Developers. It's quick & easy.

Need advice - Remoting

P: n/a
Hi, all
This time I need advice - no help ;)
I have following architecture:
30 server with 100 devices connected each one
Each "device" implement some (between 1 and 10) different interfaces
All devices implements one basic interface
I have N clients to work with all devices.
Options of implementation
1) Remoting - Owful "overhead" (IMHO)
2) Just regilar custom TCP (sending well-known string commands to hub server
to transfer to other servers)
3) Anything else
4) Your opinion


Tamir Khason
You want dot.NET? Just ask:
"Please, "
Nov 16 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Hi Tamir,

Thanks for your posting. As for the scenario you mentioned, as my own
opinion, I think the RAW socket with wellknow strings will be more flexible
since we can do anything we want via defining different wellknow strings.
And as for ..NET REMOTING, since you mentioned that your device have some
set of interfaces, using remoting will make the your application more OO
like. In addition, generally we use remoting when we want to call the
remote server object from clientside. If there're needs that the server and
client can both call the opposite, maybe socket is better.
Anyway, the realtime performance is the most important and we can do some
simple tests against both means before decide which one to use.

Steven Cheng
Microsoft Online Support

Get Secure!
(This posting is provided "AS IS", with no warranties, and confers no

Nov 16 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.