On Jun 12, 2007, at 12:09 PM, Jeff Genender wrote:
David Blevins wrote:
I guess we never really talked about how each server would get the
list
of peers in the cluster. Depending on how we do that, we could
return
to the md5'ed list idea but not the way it was proposed where the
hash
would be calculated by both sides on every request -- at least that's
the way i read it.
Nah...I think we calculate it on the server when the cluster
changes and
that becomes the version number that is sent to the client. The
client
doesn't need to worry about any calculations, and the server will only
test if the version has changed in order to send down a new copy of
the
version and list. Therefore its a calc that only happens very rarely.
How does that sound?
I think that might have been an Amelia "no" (i.e. a yes). You saying
you like the idea of the server sending the md5 down and having the
client simply send it back, no inspection on the client side -- i.e.
the version number idea from before but sending the md5 as we would
have sent the version number? Or are you referring to the same
version number idea as before?
-David
