Ted Ross wrote:
1) Make the local tag a configuration item for the broker (vhost
actually). This can be supplied in the command line or may be set
by a remote management console. The tag is stored persistently and
need be set only once.
Upon some thought (and off-list discussion with Carl), it seems that
requiring the admin to configure unique tags in all the brokers is not a
good idea. It might well be that there are multiple admins for multiple
subsets of federated brokers.
Given this, it seems easier to use UUIDs for broker tags. This removes
any need for administrative involvement but it also increases the size
of the tag somewhat.
Here's my main question. If we move from a string-based tag (right now
tags are represented as strings and lists of tags are comma-separated)
to a binary tag, we will more likely use arrays of vbin8s as opposed to
comma-separated strings. Should this be implemented in a
backward-compatible fashion? In other words, should I add a new
parameter for binary tracing and leave the string-based one intact and
handle both cases? This would allow federation interop between M3 and
M4 brokers.
An alternative is to use a string representation of the binary data
(i.e. hex or base64) but this further increases the size of the tag on
the wire.
-Ted
