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

[James Carlson]

Simon Sun writes:
> James Carlson wrote:
> > What (if anything) will be done with the existing SIP library and SIP
> > proxy that are already in OpenSolaris?
> >   
> Nothing needed for the current SIP stuff since there's no conflict 
> between each other.

What happens if someone tries to use both SIP proxies on a single
system?

What happens if a process ends up with both SIP libraries linked into
it due to library dependencies?

(I'm guessing the answers are that things may break, and, since it's
just an "option," we don't really care.  Is that right?)

> > Will the documentation say anything about the duplication? 
> I'm not sure since it's difficult to describe this very clearly. If 
> needed, any suggestion?

At a minimum, we have to tell people which implementations are the
preferred and supported ones.  See the PAC advice delivered as part of
PSARC 2009/147 ("tcpdump"):

  When  delivering  multiple  implementations  of   a   single
  feature, and where an extended period of co-existence rather
  than eventual replacement is expected, the Solaris  PAC  and
  the  management  of  the  on-going "familiarity" project are
  advised that the ARC requires explicit information regarding
  which  of  the  co-existing  implementations  is regarded as
  "preferred."

The short answer is that OpenSolaris is supposed to be a coherent
system, not just a random assemblage of parts.

> >  How should
> > developers working on SIP applications on OpenSolaris choose between
> > them?
> >   
> oSIP is an GNU open-source project and the interfaces are quite 
> different from which in SIP. The end user can make the decision on using 
> which. With libosip2 integrated, we provide the end user another choice.

Or just architectural confusion.  It's unclear which we get.

> > Is there anything that uses or will use this new library?
> >   
> Another library named libexosip2 will use it after being put back.

Is there any _application_ that will be using it?

-- 
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