.net - C# IPC Recommendations and comparisons -
I've been working in the Net for a few years, and this is my first visit to the IPC. I know of various possibilities to do IPC (named pipes, remoting, clipboard management, Win32API messaging), but I do not know what is "right for me". I am planning to use the following setup:
Site object: This is the reason that the IPC is required. This will be the only object representing the collection of files on the remote object (can be local, can actually be remote)
Server: Server. The Exe process will monitor the file system mentioned above, and will update the site object. This process will then keep any customer connected to the updated server, so that new copies of site object will be at regular intervals (either customer compulsory updates, or servers Automatic updates).
Customers: Regularly need to be updated about "site". This site also wants the ability to modify the object (or at least for the server to make specific modifications to the message
TL; DR version: Singleton Example on the server (which can be actively modified singleton), with multiple clients monetizing a singleton, the customer can change the singleton (or the server Bad
Note: Not all .NET is a mix of platforms. I remoted, but it seemed to be out of context of the context that I want to do (or I
I'm not sure whether it is better for a community wiki, feel free to jump it off.
Thanks
.NET Remoting is the only Net 2.0 feature - technology and reusable A set of Kalyon common inter-process commutation method (named pipes, network sockets, HTTP post / get query) using simple
WCF in .NET 3.0.
So the song, for you: use the TCP socket between machines on the secure LAN, internet on a machine and HTTP (soap, webmooths or just HTTP) processes (client and server) Which platforms (.NET 2.0 Remotting or .NET 3.0 WCF) - this is for you.
PS: I still use the .NET 2.0 Remoting framework.
Comments
Post a Comment