c# - Server Push vs Client Pull for Agent-Server Topology -
I need to create a system with two components:
-
A single server Which processes the data and stores it periodically sends updates to agents
-
Multiple agents that are installed on remote endpoint collect data (often But not always) long-running operations, and this data needs to go to the server
I am using the Net, and ideally I want to use the communication method in accordance with standards (i.e. one that can work with Geo, because we can also use Java agents in the future). Is there any alternative to web services?
- What are my options?
The way I see, I have 3 options using web services, and have made the following comments:
- Client pull
- <
- Client pull
- Push the server
- <
- Hybrid
- Port on Open Agent, because it both a client and server
- no polling is; The server removes the update when it is required,
'hybrids' (where the agent is both clients and The server seems obvious - but this app will usually be installed in enterprise and government environments, and I worry that there may be a problem opening a port on the agent. / P>
Does any other professional and opposition I do not remember?
Our friends swear by bridge based system:
A major reason for liking client-pull at server-push is that clients may be down, and clients should generally implement all operations pushing by all servers. If these criteria are not important in your case Maybe, their conclusions will not be your conclusions, but I guess Confirms that it is worth reading the "push versus pull" section of your paper, to define yourself.
Comments
Post a Comment