Re: [infinispan-dev] Shipping logical address String in Hot Rod protocol v1.1?
On Wed, Nov 30, 2011 at 9:46 AM, Bela Ban <bban(a)redhat.com> wrote:
On 11/29/11 6:16 PM, Dan Berindei wrote:
>> The underlying UUID would be printed (not a nice sight !)...
>>
>
> Hmm, I sometimes see UUIDs in the test suite logs. This makes me
> think, can we rely on the discovery protocol always giving us the
> logical names of the other cluster members during/after the
> viewAccepted() callback?
No, you can't. For example, if someone did not list *all* IP addresses
in TCPPING.initial_hosts, we would not get the logical names of some
members.
Ok, so using the logical names is definitely out.
>> Can't you grab the UUID which is 2 longs and simply send 2 longs across
>> the wire ? The UUID is guaranteed to be unique.
>>
>
> If we commit to sending a UUID to the HotRod clients it will be harder
> to send something else in the future. One of the reasons we chose to
> send a string was so that we could change the way we generate that
> string without breaking the clients.
Why don't you send the UUID as a (16 byte) string then ?
Yeah, that would work. However, a UUID is not always a valid UTF-8
string, so we should probably define it in the protocol as an array of
bytes (without any meaning).
--
Bela Ban
Lead JGroups (http://www.jgroups.org)
JBoss / Red Hat
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev