Thanks everyone for the perspective.
Created a JIRA entry to track the option 2 as expressed
in this thread.
On Wednesday 19 September 2012 10:07 PM, Nitzan Nissim wrote:
type="cite">We share the majority
As others have said, #2 makes
both due to the tight schedule constraints and since #3 sounds
belongs in a layer above the SIP servlets container, and could
have a separate
set of standards defined for it.
SIP Container Architect, WebSphere SIP Infrastructure
IBM Software Group, AIM
Israel Software Lab
+972 (54) 6976107
+972 (8) 9482326
09/13/2012 12:35 PM
Here are the options proposed in yesterday's meeting for
simplifying the SIP Servlet API.
1. Small Changes :
Make incremental changes to the apis. Eg: Add more
to existing interfaces like B2BUahelper etc. Do nothing
2. Big Changes:
- Utilize Java EE 6 and 7 features to simplify the
- Eg: Define JCDI custom scopes like SipSessionScoped or
SipApplicationSessionScoped, Use JCDI @Observes to
to SIP messages, Use AsyncContext of Servlet 3.0
for SIP etc.
- Make the API more pluggable to add utilities/services
generic way. We only have B2BUaHelper now.
3. Huge Changes:
- Standardize high level communication services like call
Instant Messaging and Presence.
Please reply with your opinion. Also note that, we are only
the scope for now.