-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Will Kamishlian wrote:
| It'll happen. We need to document the architecture and code | structure for Jabberd 2 in order to encourage developers to write | transports, etc. for it. I'd be happy to do the documentation; | however, I can't read C.
Understand that jabberd 2.x doesn't use in process transport in the same way that jabberd 1.4x does. That is a big reason I wrote JCR ... to allow a quick transition from jabberd 1.4x components and transports to jabberd 2.x. JCR makes the transport a stand alone binary.
Now, all we have to do is port AIM-t and MSN-t (and all the others) over to JCR to remove all dependencies on jabberd 1.4.
Regards, Paul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA7JRQ42UCbgBTOCYRAjT/AJ9gW829DWwtFcxkxqBBUFywBAOcDQCbBSPi I31KBkuk1Nch9+vE24VqHpY= =jhhb -----END PGP SIGNATURE----- _______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
