Woof! On Fri, Jan 29, 2010 at 1:15 PM, Paul Mossman <[email protected]> wrote: > Why not put it in validusers.xml? That seems like the logical place for > it.
Because validusers.xml is potentially very large with thousands of users, and changing it and replicating it due to change the USER makes on a whim (not the admin) was deemed incorrect (by Damian and myself). Another reason is because sipXecs is supposed to be able to be run WITHOUT sipXconfig even there. Currently in sipXivr there is one exception to that--a user cannot change her passcode from the TUI if sipXconfig isn't up, but that's supposed to be a not very often event (and the passcode is 'owned' by sipXconfig so it makes some sense). sipXivr is supposed to maintain it's own data, in an opaque format, and sipXconfig (and portal) are supposed to request them from sipXivr, not the other way 'round. There are still many reasons sipXivr and sipXconfig/portal must live on the same system, and removing them one by one is a good idea. SipXconfig's direct reading/writing of mailboxprefs.xml was just one of those (and it caused data to be lost), so it was to be replaced by having sipXconfig use REST to read/update it via sipXivr. That sipXivr doesn't have an https interface was just laziness on my part, as it didn't need it (and thus by extreme programing principles it wasn't done). By all means change that if you wish, but beware there are still many other reasons the two must remain co-resident. --Woof! _______________________________________________ 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/
