David Blevins wrote:
> First quick thoughts. You likely don't need the client to create the > hash, no reason the server can't send the hash it has at the time it > sends the URIs. > For that matter, it doesn't have to be a hash, it could > simply be a version number. I.e. instead of the server creating a hash > for the current URI set, it could simply give them a version number (one > byte) which it will increment on every change to the URI set. Then > using the same logic you mention, if the server sees the client has a > different number it will send the URIs + version number back to the > client with the other data. > > Thoughts? > Yep...that works too...and it's less computational overhead...works for me. I am assuming much of this code will go in the JNDIResponse, correct? Are there other objects I may need to be aware of or implement this within? Jeff > -David
