libosip2 [LSARC/2009/277 FastTrack timeout 05/10/2009]

[James Carlson]

Simon Sun writes:
> > Please indicate which one of these two will be "preferred" and what
> > the documentation will say.
> >   
> I'd express it explicitly in man page of libopsip2 like this:
> 
> Solaris provides another library named libsip for SIP development 
> purpose.  We'd suggest you to consider using it instead.  Please check 
> the man page libsip(3LIB) for more info and refer to the developer guide 
> at http://docs.sun.com/app/docs/doc/820-0643.

That seems reasonable; thanks.

> > In particular: when future projects come to the ARC and propose to be
> > dependent on libosip2, should we tell them that they need to use
> > libsip instead?
> >   
> Since I'm not quite clear the criterion of ARC, my suggestion is like 
> this. If it's an existing application and depends on libosip2, no need 
> to let he/she change to libsip since it means the code should be 
> rewritten from the beginning. If not and it's a brand new project for 
> SIP, ARC can ask them to use libsip.

OK.  That's the bit of policy information I was looking for.

> > Are these being delivered by this or by some other project?  And do
> > any of them work with the existing libsip?
> >   
> These application will not be delivered by this case and I'm not sure if 
> someone is working on porting them. None of them works with libsip.

I urge the project team to consider bringing in at least one
application that makes use of this library.  Libraries without
consumers are, in my opinion, just baggage.  And in this case, given
that the library also represents functional duplication, it doesn't
provide much of an offsetting gain.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677