Skip to main content

RE: Re: API simplification scope

  • From: Kristoffer Gronowski < >
  • To: " " < >
  • Subject: RE: Re: API simplification scope
  • Date: Fri, 14 Sep 2012 13:46:32 -0400
  • Accept-language: en-US
  • Acceptlanguage: en-US

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 
end anyways.

//Regards Stoffe 

-----Original Message-----
From: 

 
[mailto: ]
 
Sent: Friday, September 14, 2012 10:36 AM
To: 

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.

Regards
Eric


API simplification scope

Binod 09/13/2012

Re: API simplification scope

Jean Deruelle 09/14/2012

Re: API simplification scope

Binod 09/17/2012

Re: API simplification scope

Wei Chen 09/15/2012

Re: API simplification scope

Binod 09/17/2012

Re: API simplification scope

Thomas Leseney 09/18/2012

Re: API simplification scope

Nitzan Nissim 09/19/2012

Re: API simplification scope

Binod 09/20/2012

<Possible follow-up(s)>

Re: Re: API simplification scope

cheung 09/14/2012

RE: Re: API simplification scope

Kristoffer Gronowski 09/14/2012

RE: Re: API simplification scope

TIMONEY, DAN 09/14/2012
 
 
Close
loading
Please Confirm
Close