On Sep 24, Tim Bunce wrote:
> On Fri, Sep 21, 2001 at 12:33:42PM -0400, Kirrily Robert wrote:
> > In perl.modules, you wrote:
> > >Not really. Jabber is not just an IM or chat system. Jabber is
> > >a development architecture and platform for building distributed
> > >services, just as e.g. Apache is a development architecture and
> > >platform for building services and so on. Many of the developments
> > >I and other people are doing with Jabber have nothing to do with
> > >Instant Messaging. Jabber doesn't really belong in this area.
> >
> > In this case, I think DJ is right. I know I'm usually
> > anti-toplevel-namespace, but Jabber *is* a broad application with wide
> > recognition, and I don't think it's wrong in this case.
>
> Exactly. It's as important to create new toplevel-namespace's where
> appropriate as it is to avoid them when not.
>
> The judgement's fairly easy here, but sometimes requires a far-sighted
> crystal ball.
Sorry for taking so long to chime in.
From what I've read, Net::Jabber is still most appropriate. Jabber
_is_ good for many things, but you're still talking about dealing with
network protocols, no? Apache is a top-level namespace, but it's rife
with modules that twiddle the innards of Apache.
- Kurt
P.S. I know a lot about Jabber. I was the first person to port the
server to FreeBSD.
