This sound real cool.
Are you doing it as a server or command line call?
As for packaging, I think org.jabber.xdb is prefferable since that's
what it is. And anyone familiar to Jabber server will know that xdb
is the backend to Jabberd.
Licensing -- Most of the Jabber stuff falls under JOSL but an
Apache or BSD license would be ok by most people, but GPL
probably wouldn't (at least it would limit to the places where it
might get used). However, note that under JOSL, Apache/BSD
people can take it, & compile it into their code & can add
proprietary extensions. That may or may not matter to y'all.
Mark
On 17 Apr 01, at 16:08, Matt Diez wrote:
> We've got the beginnings of an xdb backend written in Java, and
> are presently looking to make it open to the public.
>
> Presently it supports registration and authentication over the
> jabber:iq:auth:0k namespace, handles rosters, and temporary
> vcards (offline message and filter support will be forthcoming).
>
> It should be able to talk to just about any JDBC friendly
> DBMS (although at present most development has been
> on PostgreSQL). So, this should take care of Oracle, MS SQL 7.0,
> DB2, etc, etc, etc.
>
> The point:
> I was rather curious if any of you had any suggestions as to how
> best to package this. I was thinking that something along the lines
> of: org.jabber.xdb or org.jabber.backends.xdb
>
> Similarly, I'd like to know about any licensing issues I should be
> made aware of.
>
> Any suggestions would be greatly appreciated. (Presently, we're
> looking at putting up a Sourceforge site, etc, etc, etc).
>
> Matthew D. Diez
>
Mark Wilcox
[EMAIL PROTECTED]
Got LDAP?
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
