Feature #29

Ability to force disconnect remote clients

Added by Curtis Hall about 1 year ago. Updated about 1 month ago.

Status:New Start:08/09/2009
Priority:Low Due date:
Assigned to:John Brooks % Done:

0%
Category:Client Spent time: -
Target version:2.0 Estimated time:8.00 hours

Description

In at least one case, I have had the server believe incorrectly that a remote client was connected, and as such, the server was feeding it data. This resulted in additional cpu time spent feeding a client that did not exist. There should be a way, for this and other reasons, to be able to manually disconnect a remote session connected to the server.

History

#1
Updated by Curtis Hall 7 months ago

  • Project changed from Bluecherry to v2-todo
  • Category deleted (Remote Client (Windows) )
  • Target version deleted (2.0)

#2
Updated by Curtis Hall 7 months ago

  • Target version set to 2.0

#3
Updated by Curtis Hall 7 months ago

  • Category set to Client

#4
Updated by Curtis Hall 7 months ago

  • Project changed from v2-todo to Bluecherry
  • Category changed from Client to Client
  • Target version deleted (2.0)

#5
Updated by Curtis Hall 7 months ago

  • Target version set to 2.0

#6
Updated by Curtis Hall about 1 month ago

  • Assigned to changed from Curtis Hall to John Brooks

Also available in: Atom PDF