[JDEV] Jabber and Enhydra

[Al Sutton]

I was looking at it the other way round. JMS being the API, Jabber being the
queuing/transport system :).

Al.

----- Original Message -----
From: "Edward J Becker" <Sauron at mediaone.net>
To: <jdev at jabber.org>
Sent: Friday, December 01, 2000 8:22 PM
Subject: RE: [JDEV] Jabber and Enhydra


> I think JMS would be useful.  I would like to be able to see the ability
to
> use third party message queuing systems as Jabber's backend... JMS would
be
> one, MQ Series would be another, I suppose.
>
> Edward
>
> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> Al Sutton
> Sent: Friday, December 01, 2000 12:07 PM
> To: jdev at jabber.org
> Subject: Re: [JDEV] Jabber and Enhydra
>
>
> I'm open to any ideas that anyone has. I'm not developing the classes to
> meet a need I have, I'm integrating Jabber functionality into Enhydra in
the
> event that someone will find it useful.
>
> I've already started looking at putting a JMS based front end on the
library
> to broaden it's appeal.
>
> Do people think this would be useful?
>
> Al.
>
> ----- Original Message -----
> From: "Thomas Charron" <tcharron at ductape.net>
> To: <jdev at jabber.org>
> Sent: Friday, December 01, 2000 2:14 PM
> Subject: Re: [JDEV] Jabber and Enhydra
>
>
> > From: "Al Sutton" <al at alsutton.com>
> > Subject: [JDEV] Jabber and Enhydra
> > > All,
> > > The idea of integrating my Jabber messaging library with the Enhydra
> > > application server (http://www.enhydra.org). I was wondering if anyone
> has
> > > any thoughts on what should be done and how it is best to do it.
> >
> >     Well, I guess it depends on what you want to use Enhydra for
exactly..
> > I'd imagine if you wrapped up the actual functionality into a Enterprise
> > Bean, you could create the bean, and throw a client front end behind it.
> > I'm not sure what the overall memory footprint of the bean would be,
which
> > may designate how usefull it'd be, but that'd be one good use for it.
> >
> >     An even better use would be to extend your classes to support
> > transports/services.
> >
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev