On Wed, 2010-02-10 at 12:22 -0800, George Niculae wrote: > > --- On Wed, 2/10/10, Scott Lawrence <[email protected]> wrote: > > > > > - per my understanding - peeridentities.xml will be > > declared as > > > <osconfig> resource in sipxbridge-process.xml.in > > and > > > sipXproxy-process.xml.in > > > > It should be a <file> resource - whether or not it > > requires a restart is > > a different unrelated question. > > > > Thanks, I had doubts on this one :) - I recall some places where > similar xml files are declared as osconfig, not file. Care to explain > the usage / difference?
At the moment, there isn't any - they are effectively synonyms. The original intent was that osconfig would be used by the files that use the syntax required by the OsConfig class in the C++ components (the *-config files). There is a set of XML RPC primitives that provide a way to manipulate entries in such files without transferring the entire file, so if we use the osconfig element to declare them, then those primitives would know which files they apply to and which they don't. At present, we don't use those primitives, so 'file' and 'osconfig' are effectively the same thing. _______________________________________________ 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/
