• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Client Crash

 
Louis Logan
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have the one instance of remote object bound to registry.
If a client crashes, how do I identify it?

I let the user optionally set the lock timeout period(or not enforce it).

But not sure if it is a clean approach.
Help appreciated.
 
Jeroen T Wenting
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can't detect it. You can only detect if there are any connections to the Remote at all, not where they are coming from, so you cannot determine whether any specific client is still connected or not.
 
Louis Logan
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jeroen T Wenting:
You can't detect it. You can only detect if there are any connections to the Remote at all, not where they are coming from, so you cannot determine whether any specific client is still connected or not.


Hm.. is it ok just to mention that the server does not keep track of
client crashes and go ahead ?
 
Mark Smyth
Ranch Hand
Posts: 288
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Louis Logan:


Hm.. is it ok just to mention that the server does not keep track of
client crashes and go ahead ?


Yeah once it is mentioned in your choices.txt that will be fine. I think that dead clients/locks handling is a bit beyond the scope of the project and I don't believe you would get any extra credit for all the additional work it would entain.

Regards,
Mark.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic