On Tue, 2009-12-08 at 14:44 -0500, Dale Worley wrote: > > IIRC, we limited "push" to a single update number just to simplify > coding the client (pushing) code. The XML RPC accommodates a separate > update number for each registration pushed. (See section 5.8.3 of > sipXregistry/doc/SyncDesign.txt.) I wonder whether the server code > for > this RPC will function correctly if it receives a "push" with multiple > update numbers? We may need to define a new "push" method name, and > play some compatibility tricks. (See section 5.12, "Protocol > Versioning".)
As far as I can tell from looking at the code, the only change (aside from any backward compatibility issues) would be to change a check for whether the registrations all have the same number... I'll have to think about whether or not we have to make adjustments for backward compatibility on this... _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
