We are only using 30 bit hashes, so even if it was a perfect hash it is possible you could get a collision. Having said that our collision space is only the single web request, so should reduce chances of error.<br><br>Toby<br>
<br><div class="gmail_quote">2009/4/1 Martin Langhoff <span dir="ltr"><<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, Mar 30, 2009 at 8:26 PM, Toby Collett <<a href="mailto:thjc@plan9.net.nz">thjc@plan9.net.nz</a>> wrote:<br>
> There is no error checking in the encoding itself, this is assumed to be<br>
> taken care in other layers, and we through in a strong hash on the whole<br>
> file to make sure this is correct.<br>
<br>
</div>Is that right? I thought what Rusty was saying re crcsync is that crc<br>
is strong, even when rolling?<br>
<br>
cheers,<br>
<div><div></div><div class="h5"><br>
<br>
m<br>
--<br>
<a href="mailto:martin.langhoff@gmail.com">martin.langhoff@gmail.com</a><br>
<a href="mailto:martin@laptop.org">martin@laptop.org</a> -- School Server Architect<br>
- ask interesting questions<br>
- don't get distracted with shiny stuff - working code first<br>
- <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>This email is intended for the addressee only and may contain privileged and/or confidential information<br>