c# - Cross client GUI update -
This is my simplified scenario, each client has a PC on LAN:
Customer 1: Add Maximum Number: _ Maximum Number: 0
Client 2: Add Max Number: Maximum Number: 0 < hr> then saves " 1 " as the maximum number of Customer 1 and Client 2 will automatically update and receive changes To:
Customer 2: Add maximum number : _Maximum number: 1 (last updated on 23/04/2014 by Client 1)
1-Voting: DB servers in regular intervals for each user's update:
itemprop = "text" Asking:
Pros: Easy to implement, safe cons: excessive bandwidth and consumption of DB server process 2-centralized TCP server: A dedicated machine Listens to the connection, each client connects to it and informs events, the server redirects those events to the related client.
Pros: Minimum bandwidth, not necessarily much process is needed: more 3-decentralized UDP notification: If the clients are in the same LAN, You can broadcast UDP packets in that network, each customer will receive every notification sent by any client.
Pros: Minimum bandwidth, 0 process requirement, no need of central server Cons: It is not guaranteed that the packet reaches it (but usually a close lane they do). So, these are the most common ways to do this, now you have to balance your needs and choose one.
In your case, I will try the UDP, if you need to ensure packet reception, then your clients can wait for the response of an event and if they react to X If not found then broadcast the packet again, thus you will ensure the reception.
Comments
Post a Comment