Dmitri Pal <dpal(a)redhat.com> writes:
> If so, I don't have any strong preference betwen them, but I
would
> think that '.' would be more likley to conflict with other uses.
Yes that was the only reason for picking '!'. I came across conflicts
when field name has to have '.'.
I might envision that host name might become a field name in some case
for example.
'!" looks much safer to me.
Safer, perhaps, but at the cost of being different from everyone else
who uses JSON, and putting additional burden on both producers and
consumers to recognise this extended syntax.
For the record, the current Event Syntax on the wiki[1] does not allow
neither '!' nor '.' in field names, so hostnames can't become key
names
and still be valid if we follow the current syntax: they would need to
be rewritten anyway. And if they get rewritten, we might aswell do that
so we can still use dot-notation, something that is well known,
understood and expected when working with JSON.
[1]:
https://fedorahosted.org/lumberjack/wiki/SyntaxFormats
Nevertheless, whether '!' or '.', I wouldn't want either to be seen
on
the wire. In a template or property-access API, sure! That is where it
belongs, but not on the wire.
--
|8]