[zeromq-dev] Devices and config files

[gonzalo diethelm]

> > Wouldn't this be a severe limitation? Even to the point of dictating
the
> > need to search for another file format, adding to the lack of
comments
> > for JSON?
> 
> I'm experimenting with another much simpler format.  JSON is annoying
> for other reasons, insisting on commas in the right place, etc.

Ok. Any pointers yet?

> > Conversely, we could use 0xNN or \uYYY to embed a binary / Unicode
> > character and have internal routines to convert those into the
proper
> > character.
> 
> Sure.  Do we actually have use cases for binary subscriptions or is
> this theoretical?

I have seen a couple on the mailing list. I seem to remember people
explicitly including the terminating zero so that they were asking for a
specific topic and NOT a prefix.

> > I would say you are mixing concerns here. A broker would certainly
be
> > nice, but that is just a distribution mechanism. I intend to do
exactly
> > the same by having the config file accessible from a public volume
(or I
> > could even use SQLite). This still means I should have a way to
state in
> > a single place what my endpoints resolve to.
> 
> Shrug.  I've no real opinion yet, it'd be good to try different things
> and see what's simplest.

I would think you want to specify the configuration (for a device,
endpoint, whatever) as a string that can be parsed. This string could
come from a config file, a database, a broker, memory in the running
program, etc.

-- 
Gonzalo Diethelm