RE: Re: API simplification scope
- From: "TIMONEY, DAN" <
- To: "
- Subject: RE: Re: API simplification scope
- Date: Fri, 14 Sep 2012 17:57:43 +0000
- Accept-language: en-US
I agree that 2 sounds best, given the time available to us. Also, as Eric
says, if we were to standardize those higher level APIs, it would make sense
to do that in a different JSR, since it's a higher level of abstraction.
From: Kristoffer Gronowski
Sent: Friday, September 14, 2012 1:47 PM
Subject: RE: Re: API simplification scope
Ok, are we in the voting stage!?
Thought it was just listing but why wait :-)
I agree both with Eric and Jean.
#2 sounds best since #3 would take too long and probably be too narrow in the
Sent: Friday, September 14, 2012 10:36 AM
Subject: Re: Re: API simplification scope
I am also in favour of (2).
(3) is probably not feasible given the timeline. Also in my opinion a higher
level API should be decoupled from sip servlet. While a higher level API can
be implemented on top of the sipservlet API, it can also support and
integrate multiple protocols and use various technologies underneath.