[Iruka-devel] genericalization of IMCom

[Petr Klyushkin]

Hello!

I've slightly rewritten IMCom so, that new features which use new
Jabber-protocol tags (not known to IMCom) can be added without changes
to existing code.  This makes all core Jabber elements (presence, iq,
message) to be passed to their handlers with all their subelements as
a tree.  Handlers fetch information they need from such tree.

Previously tag handling was very inflexible (see JabberHandler.py and
JabberTags.py).

These changes are not compatible with IMCom CLI client, so I made them
in a separate branch called "GENERIC_TAGS".  Please see them and
decide whether we should incorporate them into trunk.  This will mean
a complete fork from Casey Crabb's IMCom.

If we will not incorporate them into trunk we will have more work
adding new features to Iruka.  I think we _should_ fork so we can
develop Iruka in any way we want.  The major drawback of IMCom is it's
lack of flexibility as a library which can slow us down in future.

I've also written some how-to info on writing event handlers, see it
in README.txt file.

To download GENERIC_TAGS branch from CVS use such command:

  cvs -z9 address@hidden:/cvsroot/iruka/ co -r GENERIC_TAGS -d iruka-gts iruka

(change "yourname" to your Savannah account name and iruka-gts to name
of directory you want this tree to go to.)

-- 
                                                             C'ya, Peter.
       address@hidden://petrk.pochtamt.ru]=--
        --=[ICQ 89449080]=--=[Jabber address@hidden

XMMS: Nightwish - Elvenpath