On Mon, 2009-06-22 at 10:08 -0400, Robert Joly wrote: > > On Mon, 2009-06-15 at 12:12 -0400, Scott Lawrence wrote: > > > Creating a new database seems best, David - indexed by AOR. > > > > Yes -- the datum you want to store is per-AOR, and there is > > no existing table that is indexed that way, or anything close to it. > > > > In the XMPP work that I am doing, I will have a need for a database that > maps an AOR to its Jabber ID. Instead of creating multiple individual > databases that map an AOR to a specific attribute, would it make sense > to have a single one which maps an AOR to a set of attributes that > applications need to access. Initially, that set of attributes would be > the custom VM time-out and Jabber ID but could grow over time to include > more attributes.
Using a separate table per mapping type would allow us to only replicate each set of data to the servers that need it. If we combine the tables, we end up replicating data to xmpp servers that are only needed by the registry, or only by voicemail, etc. _______________________________________________ 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/
