Message format?

[Matthias Urlichs]

Hi,

I'm thinking about replacing the old protocol which is used to talk to knxd (on unix sockets and port 6720). The C macros used to build the client libraries are an inflexible nightmare, esp. when transmitting more complicated data structures (think online-updating the currently-running knxd's configuration, dump status, enable debugging, authorization, etc). These days, there are better alternatives. Worse, some of the auto-generated language bindings are Just Wrong, undocumented (just try to figure out how you'd even use the generated Python bindings …), don't fit the idiom of the target language (Python again), and are unable to transmit reasonable error indications.

Yes, I'll keep the old server code for backwards compatibility. I'll just implement a new "set protocol version" message. That's reasonably easy.

Anybody got problems with using msgpack?

[Othmar Truniger]

I know that linknx uses 6720/tcp to talk to knxd. But as long as this does not get broken I don't see any problems for enhancements.