HanzZ

Support for more resources

With Jabber you can use more clients to login to your Jabber account. Every connected client has his own resource string, which allows service to make a difference between them. Resources weren’t supported by transport until today .

In the older versions, the client features were handled only for the first client which established connection. This brought a serious problem. If user connected from client which doesn’t support for example Roster Item Exchange, this feature was disabled for whole session. This change fixes it and every resource has now its own features list. It depends on resource priority which one will be used.

There is also change in message handling. If you are connected from Psi and Gajim and you start chatting with John from Psi, his responses will be sent to Psi even the Psi has lower priority. If you logout Psi, messages from John will be sent to bare JID (It means JID without resource) and it’s up to server to choose proper client. If you write him from Gajim, responses will be sent to Gajim. If somebody from legacy network starts the conversation with you, the message will be sent also to bare JID.

Another smaller change is that transport supports VCard caching. This is useful for networks like Facebook where the VCard is not changed so often. It saves bandwith and CPU time.