Re: C# remoting vs Socket ?
From: Lars Olsson (lasseolsson_at_myrealbox.com)
Date: 04/02/04
- Next message: Robert Desbiens: "Re: IIS Remoting Issue"
- Previous message: Sunny: "Re: COM component event interaction question"
- In reply to: Bruno Nogent: "C# remoting vs Socket ?"
- Next in thread: Ice: "Re: C# remoting vs Socket ?"
- Reply: Ice: "Re: C# remoting vs Socket ?"
- Reply: Allen Anderson: "Re: C# remoting vs Socket ?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 2 Apr 2004 20:18:55 +0200
In my personal experience, the current out-of-the box .net framework 1.1
remoting is NOT suitable for real world applications.
Go with sockets.
Good reading:
http://www.ingorammer.com/RemotingFAQ/RemotingUseCases.html
If your team an/or boss insists, check out the genuine channels package:
http://www.genuinechannels.com/
"Bruno Nogent" <bruno.nogent@metaxis.fr> wrote in message
news:uboDa3LGEHA.1240@TK2MSFTNGP10.phx.gbl...
> Hello,
> We develop a ticker application and we want to know what is the
performance
> of .NET remoting (C#)
> with more than 100 users for on remote objet ?
> How the threads are used ?
> How keep message order ?
>
> Thanks
>
>
- Next message: Robert Desbiens: "Re: IIS Remoting Issue"
- Previous message: Sunny: "Re: COM component event interaction question"
- In reply to: Bruno Nogent: "C# remoting vs Socket ?"
- Next in thread: Ice: "Re: C# remoting vs Socket ?"
- Reply: Ice: "Re: C# remoting vs Socket ?"
- Reply: Allen Anderson: "Re: C# remoting vs Socket ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|