[SIPSERVLET_SPEC-4] Clarify specific API in distributed environment Created: 04/Oct/12 Updated: 26/Mar/14 Resolved: 26/Mar/14
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
It would be useful to mandate certain behavior if an implementation chooses to support clustering. For example,
|Comment by keith-lewis [ 05/Mar/14 ]|
We agree that it should be mandatory for key based session targeting to work across the cluster.
We should however allow for topologies where the SAS is located on particular nodes in the cluster.
It would be good to have the following methods of the SAS always available.
The first 2 methods only need access to the SASid.
To achieve this we could require that even when the full object is not available the container should supply a "skeleton" object which implements these methods.
To allow the developer to know whther it has the "real" object we can provide a new method on the SAS called isLocalSession() (or isAvailableLocally?)
SipSessionsUtil.getApplicationSessionById() should never return null - it either returns the skeleton object or a real one.
|Comment by binod [ 26/Mar/14 ]|
We had a discussion on this in the EG meeting.
In general, it is hard to get consensus on issues related to distributed environment. This is partly due to
The conclusion was containers should have more flexibility in their topologies and implementation choices and is