Hello everyone.

The next AIM-t's XDB file name format will be different from the one
currently used.

[for admins]

!! You have to keep record of your server's logs *now* in order to
!! be able to convert you server's AIM XDB files easily to the new
!! AIM-t's XDB format.

This is done by running
grep "\[AT\] Closing down" error.log | awk '{print $9}' >> login.txt
before rotating/deleting jabberd logs.

Please see http://aim-transport.jabberstudio.org for details and further
news.


[for developers]

AIM-t up to now uses hashed JIDs for its XDB entries. This prevents easy
migration to other transports and - most important - makes fixing one
nasty long-lived bug very hard: AIM-t is case sensitive concerning the
user part of the user's JID, meaning if you register with AIM-t after
having logged on to Jabber with user "user@host" and later reconnect with
user "USER@host", AIM-t will fail to log on properly. Depending on your
further actions, you can wind up with several independent registrations
and all kinds of inconsistent AIM-t contact lists causing major confusion.

BTW most other transports have this bug, too.

Regards
M.Kiesel

_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

Reply via email to