On Jun 12, 2007, at 3:35 PM, Jeff Genender wrote:
David Blevins wrote:
I think that might have been an Amelia "no" (i.e. a yes).
Hehe! I know that "No" too ;-)
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?
Kind of a hybrid. The MD5 would be the number...that is the "version"
so-to-speak. Server will check if that number matches its own (it was
calculated when it first had a cluster setup). If they are the same,
its business as usual. If the cluster changes, then the server
changes
its number and then there is a difference the next time the client
comes
knocking. Thus an update will occur.
The reason why I like to use the MD5 as the version number is all
servers theoretically would calculate the same MD5 (or even a simpler
lighter algo) and thus always have the same version number w/o
having to
share that between all servers.
Cool, that's what i was saying. The version idea where the md5 is
the version. We're on the same page.
-David
