[JDEV] Net::Jabber

[DJ Adams]

>
> 1 - Is Net::Jabber comprehensive enough to also use it to write
transports?
> Or is it mostly client stuff?

Sticking my neck out I'd say yes it is, not least because of the fact that
both the Client.pm and Component.pm (Transport.pm is now deprecated) are
fairly thin wrappers around the Protocol.pm engine; after all, once the
transport (small 't') is connected, the implementation is down to
Protocol.pm anyway... and Protocol.pm implements agent and register stuff,
for example.

But I think this is one that Ryan is much better placed to answer.

> 2 - Suppose a huge site (10000 users) wanted to use the email
notification,
> then every time the presence detection would see for example 5000 users
> online, filters out the one it is looking for, etc. That's not very
> effecient. Is there a way to ask not to receive any presence information,
but
> rather for the client to be allowed to simply ask the server about the
> presence for a particular user?

Well, for a another angle how about splitting the task into two, and have a
'daemon' type part that is constantly connected to the Jabber server (and
therefore has all the presence at hand) and a 'squirt' part which tells the
daemon to send a Jabber message. Hmm, this is sounding more and more like a
transport/component thingy task ;-)

dj