You are right when we use a SHA1 hash, I'm not sure what I was thinking there.
I hope client developers start implementing this XEP. I only know two
implementations so far. If it was widespread we could implement something like
http://brightkite.com/ using XMPP!
Date: Fri, 31 Oct 2008 10:50:20 +0200From: [EMAIL PROTECTED]: [EMAIL
PROTECTED]: Re: [jdev] GEOLOC Support
I misunderstood the purpose of the hash. I thought the client was expected to
unhash it and use it to determine the capabilities. I didnt realize it was used
to compare caps efficiently.
Hashes are one-way, so it's very hard (i.e. you often need to brute force), to
reverse the calculation. Hashes are a quick and easy way though to compute a
'fingerprint' for a set of data, so that you can easily determine if you've
seen it before (by comparing the hashes), or not (and then you can do the
'expensive' disco query to get the data that the hash was computed from).
Clients need to store the disco result along with it's hash, so that when they
see the same hash again, they know what the result was, and they don't need to
re-query it.-- - Norman Rasmussen- Email: [EMAIL PROTECTED] Home page:
http://norman.rasmussen.co.za/
_________________________________________________________________
Store, manage and share up to 5GB with Windows Live SkyDrive.
http://skydrive.live.com/welcome.aspx?provision=1?ocid=TXT_TAGLM_WL_skydrive_102008
_______________________________________________
JDev mailing list
FAQ: http://www.jabber.org/discussion-lists/jdev-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [EMAIL PROTECTED]
_______________________________________________
