2009/4/24 Christoph Terwelp <m...@seark.de>: > > Am 24.04.2009 um 14:10 schrieb Matthew Wild: > >> On Fri, Apr 24, 2009 at 1:02 PM, Christoph Terwelp <m...@seark.de> 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. >
I think you are complicating things way too much. If the client's cache gets corrupted, it probably isn't loadable anyway. I would let the ver be opaque for client. The implementation notes would then simply explain the ideas behind minimal implementation with hashes and more sophisticated implementation with integer numbers.
