(This got held up by the updating of the SipFoundry servers.) On Wed, 2009-05-27 at 10:56 -0400, Carolyn Beeton wrote: > I'd like to solicit opinions on whether building an AppearanceAgent by > reusing large parts of the RLS code is a good idea or not.
It would help if there was any serious documentation for how the RLS works. That was one part of the BLF project for which time was not allocated. But yes, some of the lower-level components can probably be shared. And having two users really helps to clean up the design of a class. > I would also like to make something which would have an evolution path: > Polycom implements draft-anil-sipping-bla-02 and has no plans to move to > anything else, but a newer version of that draft exists (just for fun > they changed the name of the event package sets subscribe to; don't know > if any sets implement it), and there is a new > draft-ietf-bliss-shared-appearances in the works also. It seems that > the reality will be a mix of stuff out there. I've heard that two versions of draft-anil-sipping-bla are used, and of course, there's the new Bliss draft. And I've been talking to Francois Audet; apparently there is a proprietary method used between A2E and the 11xx phone. With luck, these schemes are the same at a logical level, and we may be able to construct a multi-protocol BLA server by changing only surface-level behavior. (I fear market pressures will require this in the long run.) Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
