[JDEV] jabber, grove, and communcation infastructure

[Nitin Borwankar]

I have not done this but this is eminently do-able :-

Java implementations of Jabber can map Jabber messages
to JMS ( Java Messaging Service) messages.
This allows very powerful integration into enterprise
data management systems via technologies like IBM MQ Series
and it's interactions with CICS and mainframe transaction processing.

Admin commands from Jabber enabled Palm Pilots (coming soon)
can then pass via MQ Series into enterprise database systems,
either administering them, monitoring them or at the User level
initiating queries and transactions.

I could go on and on.

Contact me if you need more info.

Nitin Borwankar,
CTO, Borwankar Research Inc.,
nitin at borwankar.com



"Rolle, Ted" wrote:

> Quick, guys!  I have a manager stopping by this afternoon to take a look at
> Jabber!  He has the authority to approve continuation of my intranet
> implementation here...
>
> So, what I'm asking is:
> What sorts of things can Jabber be used for, besides Instant Messaging;
> what's currently being worked on?  What's in the planning stage?
>
> The Instant Messaging of Jabber might be enough to "sell" it, but my vision
> is that it can be used to transmit files to users, process control,
> whatever....
>
> Eagerly awaiting replies-ly
>
> Ted
>
> -----Original Message-----
> From: Thomas Muldowney [mailto:temas at box5.net]
> Sent: Thursday, November 16, 2000 11:59
> To: jdev at jabber.org
> Subject: Re: [JDEV] jabber, grove, and communcation infastructure
>
> This is exactly what Jabber was designed for, it just happens that IM is the
> first (and easiest) case example.  As St. Peter mentioned PocketLinux is
> using
> Jabber for just about everything it does, very neat!  I also know of help
> desk
> management solutions, and system monitoring solutions built on Jabber's
> ideas.
> I would expect to see a lot more coming out soon along lines other than your
> standard "IM" fair.
>
> --temas
>
> On Wed, Nov 15, 2000 at 10:58:05PM -0500, kellan wrote:
> > i recently went to a little presentation on groove (groove.net) which is
> > ray ozzie's new collaboration tool/network.
> >
> > groove has been running as one of those high profile stealth-mode
> > companies (like transmeta) so i was pysched to see a little of what they
> > had been working on.(remembering vaguely that they had finally come out of
> > the closest, but having not had time to follow up)
> >
> > groove, in a sentence, is a p2p (whatever that means) groupware app,
> > messaging, shared spaces, collaboration, etc.
> >
> > i first perked up my ears when i heard the term "groove communicates
> > between servers and clients via an xml stream of deltas".  well the phrase
> > "xml stream" made me thing of jabber, and that is how i thought of it for
> > the rest of the presentation.
> >
> > users can communicate directly peer-to-peer but will often find each other
> > through servers.  these servers handle registering presences (jabber
> > again), and use transports(!!) to be "device agnostic", i.e. talk to cell
> > phones and whatever other gadgets people have.
> >
> > so my question is, is jabber being used for anything like this?  in the
> > backend, to provide the communications framework for an application?  how
> > suited is jabber to this sort of role?  in my shallow analysis of the
> > space it would seem like jabber would be very suited to this.
> >
> > any thoughts, feedback?
> >
> > kellan
> >
> >
> >
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
>
>   ------------------------------------------------------------------------
>
>    Part 1.2    Type: application/ms-tnef
>            Encoding: base64