By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,458 Members | 1,463 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,458 IT Pros & Developers. It's quick & easy.


P: n/a

Some basic advice needed for a C# semi-newbie:

I have a server program that exposes a Singleton object (lets call it
"ServerObject") to a number of clients, using Remoting.

Clients call a method of ServerObject, which returns an object (call it
"ObjectToProcess") to the client. Upon receiving this ObjectToProcess, the
client performs some analysis (actually performed by a human), and sometime
later the ObjectToProcess is returned to the ServerObject.
A client can hold more than one ObjectToProcess at a time (that is, a client
can ask for a second object before returning the first).

So far, I have the above communication working.

My goal: I would like to start a timeout timer on the server for each object
that is doled out to the client. If the timer times out (i.e. the client has
not returned the processed object in the allowable time), the server should
sever communications with the client.
When the timer times out, I would also like to know which object and which
client timed out.

1. How do I start a unique timer for each ObjectToProcess that is sent to
clients, and wire up an event for the timeout? (Each ObjectToProcess has a
unique name, number, etc.)

2. When a timer times out and fires its timeout event, how can I keep track
of which object and client were originally associated with this timer?

3. <Optional Remoting question> How can I sever communications with the
client such that the next time the client tries to access the server object,
an exception is thrown on the client?


Nov 15 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.