[JDEV] Java C2S Components? (for connecting to regular 1.4.x)

Katz, Dov B (IT) Dov.Katz at morganstanley.com
Wed Jan 21 16:19:46 CST 2004


Think of this as more of a challenge, and less of a development
direction, commitment to a particular version etc... 

1) I'd like to get it working with 1.4.x, then I can explore and rewrite
for 2.x...   

2) I know about jab2+jadc2s, but let's explore this challenge in a
vacuum for the sake of seeing how it can be done

3) it shouldn't matter in theory, since my point is that I want it out
of core, and running via component:accept.

Java might be good if you plan on embedding it an existing java-based
infrastructure, but for now let's abstract away all languages....

What is the xml between the c2s and sessions/jabber jsm after a
component:accept connection is established to:

1) create a user session
2) destroy one
3) receive and send IM presence, messages, and IQ's

Thanks
-Dov

> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org] On 
> Behalf Of Peter Saint-Andre
> Sent: Wednesday, January 21, 2004 5:13 PM
> To: jdev at jabber.org
> Subject: Re: [JDEV] Java C2S Components? (for connecting to 
> regular 1.4.x)
> 
> On Wed, Jan 21, 2004 at 04:56:04PM -0500, Katz, Dov B (IT) wrote:
> > Thanks. That part (and I'm tooting my/our horn here) we are 
> able to do via our jabber gateway framework (JGF) which we 
> are releasing to open source. 
> > 
> > I'm looking in particular for the message exchange between 
> C2S and sessions component, etc, once connected...
> > 
> > I'm trying to rewrite C2S to host it outside the jabber server for 
> > accepting client connections, and notifying the server for creation 
> > and destruction of them, etc...  Does anyone know the 
> message exchange 
> > needed to do this/
> 
> That's not part of the standard protocol defined by the 
> JSF/IETF -- it's really implementation-specific, and jabberd2 
> uses a different protocol (I think) than jabberd 1.4.x does. 
> So you have a couple questions to ask
> yourself:
> 
> 1. Do you want to be tied to jabberd 1.4.x?
> 
> 2. Can you use jabberd2 + jadc2s instead?
> 
> 3. If you need this, are you use that Java is the right approach?
> 
> Understand that I'm not close to this stuff in jabberd*, just 
> providing a few questions. Others can, I'm sure, speak to 
> this with more authority than I can.
> 
> /psa
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 
> 
--------------------------------------------------------
 
NOTICE: If received in error, please destroy and notify sender.  Sender does not waive confidentiality or privilege, and use is prohibited. 
 



More information about the JDev mailing list