Ok, That is good information. I believe that due to my inexperience with this particular xmmp suite I have been talking about something that might not be possible here.
Alright, background: On my present production server, I have J2s8. If I wanted to put a virtual name (foo.jabbercluster.com) on it, I could register in DNS, and then deploy 7 different clustered servers Worldwide, each syncing databases from one to another, More like a multi-master setup, not a master/slave. This would allow me, with some interesting SRV records to point a user anywhere to his/her closest jabber instance depending on his IP address. The databases being sync’‘d would allow any user from any country to log into a wildfire server close by, authenticate to LDAP and not only authenticate properly, but also retrieve his roster from that near wildfire server and it would be as if he was at his/her computer. Searching the forums, it looks like Wildfire isn’‘t capable of actually working like the other jabber instances , in that I mean authenticate to LDAP, but store user information like rosters, bookmarks, etc in the Postgresql database that is setup on each server. On my present Production Jabber server, I authenticate to LDAP, butstore info in the pgsql db, which makes searching TONS faster. Reading the forums, it would seem that it is an either/or situation. One cannot authenticate to LDAP, and store information in another database (from what I am reading in these forums atleast), which is sort of puzzling because if you can’‘t do this, where are the contacts stored if LDAP is read-only? Although the server is interesting with it’‘s support for new add-ons, and other things; I need to be able to authenticate to LDAP, but store user information locally, for retrieval at any station that someone may walk up to and login at. If I am incorrect in my thoughts on the capabilites of Wildfire please correct me, however I can’'t find anything in the forums that says that the dual database usage is possible. to clarify, LDAP is part of our eDirectory tree in ourold Novell instance. We are switching to AD2003, but LDAP and edirectory will be hanging around for a while doing mundane authentication for things like web access, Jabber, intranet, etc. The LDAP information/user info is multi purposed and not setup solely for wildfire, in that Wildfire will never be allowed to add information to the user stores in that database, hence the need for pgsql.