Bug #357

Connecting using different connection types with the same session may cause a ClassCastException.

Added by derek clayton 542 days ago. Updated 346 days ago.

Status :Closed Start :08/11/2010
Priority :Normal Due date :
Assigned to :derek clayton % Done :

0%
Category :Clients
Target version :Union Server 1.0 Beta 2

Description

Reconnecting using different connection types with the same session may cause a ClassCastException. For example, if a client connects using a persistent socket connection and then disconnects but reuses the prior session id for an http socket connection then a ClassCastException will occur.

The server should not care about the concrete type of connection used by the client and it should be changeable within a session.

History

11/19/2010 08:43 PM - derek clayton

  • Target version changed from Pending Review to Union Server 1.0 Beta 2

02/22/2011 06:49 PM - derek clayton

  • Status changed from New to Closed

Also available in: Atom