Re: [JDEV] Re: Jabber Client Module..

[Jeremie <jeremie@jabber.org>]

>   Net::JabberClient - Jabber client module used to connect to
> transports.. 
> 
>   Net::JabberClient::Session - Jabber session module.  This is be used
> on TOP of Net::JabberClient.  This way, multiclients are VERY easy to
> write..  Just make a new Session from the JabberClient object. 

Hmmm... Why the seperation?  Shouldn't we be able to make just one module
operate in both modes, where you can just create an object for each
connection?  Or am I misunderstanding something?

>   Net::JabberTransport - Same as JabberClient, but for transports.. 

Well, 90% of the work in the transport module is 100% etherx stuff and not
directly related to Jabber at all.  I had registered the Net::Etherx
namespace with CPAN, and Jabber specific stuff could be in
Net::Etherx::Jabber for transports.

I had also registered Net::Jabber for the client stuff, since that is
simple and goes along with the rest of the Net:: namespace(mostly clients
for other protocols).

>   Here's a good question that I didn't think of before writing the
> above..  Can you actually have a MultiTransport? 

Hmmm... technically, yes, but I can't think of a reason why, since you can
use one transport to do just as much as multiple ones...

Jer