Hi all.
I have been working on a framework which I’m calling Action Messenger
for the
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
Typo
over the past day or so, and things look promisingã??so far, but it’s
going to
be difficult to fit together if I have to keep multi-blog support for
Jabber
notifications.
The way I’ve designed things (at least for greatest convenience) is for
a site
to generally only have a few messengers, but normally one.
Authentication is
by default, stored away in the config directory similarly to Active
Record,
global to the application. A site generally becomes a single XMPP
entity,
and that entity can send or receive messages.
However with the current Typo, there is separate configuration for this
Jabber
messaging agent in each individual blog. This makes using my library
not
impossible, but a little more annoying.
So I guess I’m just feeling around for opinions at the moment. I can
have a
simple, unit tested mechanism for Jabber notifications in a few minutes,
if
people are willing to sacrifice support for separate Jabber logins for
each
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
multiple
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
contacted
through DRb, but it feels a bit messy to have to do that when there are
plenty of Typo instances already running.
TX
Well, at the moment we don’t actually support multiple blogs. So,
I’mnot convinced that this is a real problem :-). For now, I
thinksupporting a single jabber login per server is okay, and we
canrevisit that when we enable multiple blog support.
Scott
On 5/15/06, Trejkaz [email protected] wrote:> Hi all.>> I have
been working on a framework which I’m calling Action Messenger for the>
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
Typo> over the past day or so, and things look promisingã??so far, but
it’s going to> be difficult to fit together if I have to keep multi-blog
support for Jabber> notifications.>> The way I’ve designed things (at
least for greatest convenience) is for a site> to generally only have a
few messengers, but normally one. Authentication is> by default, stored
away in the config directory similarly to Active Record,> global to the
application. A site generally becomes a single XMPP entity,> and that
entity can send or receive messages.>> However with the current Typo,
there is separate configuration for this Jabber> messaging agent in each
individual blog. This makes using my library not> impossible, but a
little more annoying.>> So I guess I’m just feeling around for opinions
at the moment. I can have a> simple, unit tested mechanism for Jabber
notifications in a few minutes, if> people are willing to sacrifice
support for separate Jabber logins for each> 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 multiple> 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 contacted> through DRb, but it feels a
bit messy to have to do that when there are> plenty of Typo instances
already running.>> TX>> → Email: [email protected]>
Jabber ID: [email protected]> Web site:
http://trypticon.org/> GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F
A62C B8C7 BC8B 037E EA73>>>
_______________________________________________> Typo-list mailing list>
[email protected]>
http://rubyforge.org/mailman/listinfo/typo-list>>>