I have been working on a framework which I’m calling Action Messenger
time being, which aims to provide an Action Mailer-like API for sending
messages over XMPP (Jabber.) I’ve been playing with integrating it with
over the past day or so, and things look promisingã??so far, but it’s
be difficult to fit together if I have to keep multi-blog support for
The way I’ve designed things (at least for greatest convenience) is for
to generally only have a few messengers, but normally one.
by default, stored away in the config directory similarly to Active
global to the application. A site generally becomes a single XMPP
and that entity can send or receive messages.
However with the current Typo, there is separate configuration for this
messaging agent in each individual blog. This makes using my library
impossible, but a little more annoying.
So I guess I’m just feeling around for opinions at the moment. I can
simple, unit tested mechanism for Jabber notifications in a few minutes,
people are willing to sacrifice support for separate Jabber logins for
user. Or, I can spend some more time trying to make this (possibly more
unusual) usage a little easier to stomach.
I have to do a little work to get this thing to behave better under
instances anyway – right now it works, but connects N times. I have a
working prototype of a notifier that runs separately to Typo and is
through DRb, but it feels a bit messy to have to do that when there are
plenty of Typo instances already running.