I don't know why remoting wouldn't be a good fit. You are just passing
messages back and forth to synchronize timers. You don't need to sync every
second.
With remoting, you can set up an observer pattern, so that the clients
simply tap into a published event on the server. call it the Reset event.
The server, when publishing the event, will indicate the client number,
or -1 to mean all clients, and the amount of time to start at. The server
app is responsible for keeping track of what the values are on the clients
and displaying the timers.
It's a good bit tougher if you use the TCP stack or web services, since you
have a two-way communication.
To understand remoting, pick up an EXCELLENT book by Ingo Rammer called
"Advanced .Net Remoting"
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
<ag*****@optonline.net> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
I am about to take my first crack at C# and would like some
suggestions/best practices for approaching the app I am looking to
build. Here's a simplified description of the problem :
The client application will handle displaying a countdown timer that
will be controlled by a remote administration console. I would like to
be able to assign the task of displaying the timer on 1, some, or all
of the clients. The administration console will be able to start,
pause, or reset the clock at any time. The console should be able to
display the current time left on the counter on the clients. I looked
into "Remoting" for this task, but it doesn't seem to be a great fit.
There are other tasks that the server and clients will perform, but
this is the process that will go on.
Thanks in advance!!
