On Tue, Sep 25, 2001 at 05:45:47PM -0700, Kurt D. Starsinic wrote:
>
> I'm _really_ familiar with Jabber, honest. Jabber is much more than
So am I :-)
> an IM gateway. I'm saying that there's no call for a top-level namespace
> unless the Jabber community is going to populate it with a variety of
> internals hooks, in much the same way that the Apache community has.
I've at least three packages I'm planning to upload in the near future,
Jabber::Connection, Jabber::RPC and Jabber::RPC::HTTPgate. As you can
see from the modules list this week, Piers is planning to contribute
another two: Jabber::JAX::Component and Jabber::Judo::Element, with more
to come. And I don't think that will be the last of it by any means, as
is clear from the movements in the development community at the moment.
> AFAICT, the only Jabber-related Perl modules that exist or have
> been proposed deal with "the Jabber protocol", from the network level
> (moving bits over the TCP) to the application level (building and
> parsing the XML). Ryan Eatmon's excellent and substantial offerings,
> for example, live under Net:: and XML::.
Ryan has written some great modules, but as I briefly explained in my
initial proposal, the Jabber::Connection package is a different approach.
I'm sure you're not an advocate of 'one size fits all' in software...
I certainly am not.
> If you're planning on doing something more integrated into Jabber's
> core, then I endorse a Jabber:: top-level namespace. If you just want to
> make the point that Jabber is more than IM, then I don't think the PAUSE
> namespace is the best forum for that.
I beg your pardon?
I don't understand how you turn the explanations and reasonings that I
have given in response to queries on this list into a desire on my part
to 'make a point' or use this list or the namespace as a 'forum' and am
mildly offended, to say the least.
dj
