Yes, you brought this up some time ago and we never resolved it.
As you point out doing an explicit test on the TCP connection is expensive/unreliable. So I agree the notion of 'active' is not realistic.
What the websocket protocol does give us however is are the open and close frames. I think its a useful concept for developers to be able easily to list out the connections which the protocol has notified have been opened, but have not notified that they are closed. In other words, I think its going to be a very common (and repetitive) pattern in server code to maintain a list of such 'open' connections, even if they still need to code around cases where one or two rogue connections have simply vanished without telling anyone.
I'd propose we rephrase/name these API calls to be based on what the websocket protocol gives us (open/close frames), which I think addresses the expense/reliablity issue you bring up, which relieving the developer of what I think is a common programming task.
On 11/26/12 1:00 PM, Bill Wigger wrote:
[jsr356-experts] Re: [jsr356-users] isActive() method removal from API