Am 24.04.2009 um 14:10 schrieb Matthew Wild:
On Fri, Apr 24, 2009 at 1:02 PM, Christoph Terwelp <[email protected]>
wrote:
If the ver attribute is some kind of a hash of the roster, a
additional
feature could be added, to inform the client which method was used to
generate the hash. So the client can check the current roster. This
way
corrupted rosters can be detected and no user interaction is
required.
I'd rather keep it opaque to the client. Rosters shouldn't get
corrupted during transfer, that's what TCP is for :)
I don't suggest they could get corrupted during transfer, but because
of a client malfunction or a system crash.
The hashing algorithm of each server would be different anyway, and I
don't see that clients would want to support each and every one
individually.
Maybe, but choosing a hashing algorithm in the XEP would improve the
chances that client and server do use the same one.
Christoph
