Roster


Added by Mickaël Rémond, last edited by Mickaël Rémond on May 05, 2008  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
Table of Contents

Index

Roster size limitation

  • Problems:
    1. The roster list can become very long. As the roster is used as a basis for presence broadcast, long roster consumes memory, disk space, bandwith and processing.
  • Solutions:
    1. Limit roster size

Useless roster entries

On real life server you sometimes see that you have roster entries from user that are users without the server. This is a user mistake.
In the current state of the protocol they cannot be removed or blocked because you are supposed to be able to add a server or a component in your roster. I can be in a non fully qualified domain form, so formally, you do not know if you need to send back an error. It ends up in the roster and can stay there indefinitly if the user does not remove it manually.

The ideal case would be to have several items types:

  • User: default one. Must be a full JID
  • Component: can have either a full JID or just the host part.

Clients must have a distinct addition process for both to avoid user errors.