Thanks, I'll check it out! Brian ;)
--On Monday, December 03, 2001 02:56:51 PM -0600 Thomas Muldowney <[EMAIL PROTECTED]> wrote: > Without writing a new module you'll be restricted to using client space > since you are authenticated as a client. If you become a component you > get to access XDB directly with the <xdb/> element. Here's a component > document I recently wrote if you are curious about them: > > http://docs.jabber.org/general/html/component-intro.html > > Generally it's sounding like you want to be a component to me. > > --temas > > > On Mon, Dec 03, 2001 at 12:55:16PM -0700, Brian Brown wrote: >> >> >> --On Sunday, December 02, 2001 07:54:19 PM -0600 Thomas Muldowney >> <[EMAIL PROTECTED]> wrote: >> >> > Public XML data storage is possible here is an example: >> > >> > <iq type='set' id='public_set_3' to='user@server'> >> > <query xmlns='my_namespace'> >> > <data/> >> > </query> >> > </iq> >> > >> > The few restrictions are that you can not use a jabber: namespace they >> > are reserverd by the system. The other main thing is to make sure you >> > are sending to the user. >> > >> > Another thought, are you doing something that should be a component >> > rather than a user? >> > >> >> I think that's part of what I'm trying to figure out. I am already using >> the feature you show above; what I'm after is writing to somewhere on >> the server that is not tied a specific user, so I can store server wide >> info that needs to be updated from specific clients. I found a >> reference to using alternate namespaces in the xdb config... I just >> haven't tested that yet to see if it would work. >> >> >> > >> > --temas >> > >> >> Any other thoughts? >> >> Brian >> >> _______________________________________________ >> jdev mailing list >> [EMAIL PROTECTED] >> http://mailman.jabber.org/listinfo/jdev > > -- > Thomas Muldowney > email/jabber: [EMAIL PROTECTED] _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
