Call it 1.0 ?

[Matthias Urlichs]

Any bugs / enhancements you need to have fixed/done before we call the next release 1.0?

The milestone https://github.com/knxd/knxd/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0 currently lists two: the config file format, and cleaning up the client library (no version zero, no reserved identifiers).

[Thomas Dallmair]

With a major version change I'd see at least some potential for these:

• #47 `groupsocketlisten` should print timestamp
• Change "eib" to "knx" everywhere, including build scripts and library names (yes I know, that's very breaking, but I'd rather do it in an upcoming 1.0 than never)
• (Build) scripts
• --enable-eibnetip --> --enable-knxnetip
• --enable-eibnetserver --> --enable-knxnetserver
• --enable-eibnetiptunnel --> --enable-knxnetiptunnel
• --enable-eibnetipserver --> --enable-knxnetipserver
• eibread-cgi, eibwrite-cgi
• Library names
• libeibstack --> libknxstack
• libeibclient --> libknxclient
• Type and function names, macros
• eibaddr_t --> knxaddr_t
• eibkey_type --> knxkey_type
• EIBnetServer --> KNXnetServer
• EIBOpenT_Connection and friends
• Others?

[Matthias Urlichs]

On 20.01.2017 16:15, Thomas Dallmair wrote:

• --enable-eibnetip --> --enable-knxnetip
• --enable-eibnetserver --> --enable-knxnetserver
• --enable-eibnetiptunnel --> --enable-knxnetiptunnel
• --enable-eibnetipserver --> --enable-knxnetipserver

or drop the "eibnet" part entirely.

-- 
-- Matthias Urlichs

[Thomas Dallmair]

• --enable-eibnetip --> --enable-knxnetip
• --enable-eibnetserver --> --enable-knxnetserver
• --enable-eibnetiptunnel --> --enable-knxnetiptunnel
• --enable-eibnetipserver --> --enable-knxnetipserver

or drop the "eibnet" part entirely.

Hmm, KNXnet/IP is a well-known name, so I'd rather leave that one as it is, but I must admit that I still struggle with all of these. What's the difference between eibnetip and eibnetserver? (Isn't the server using IP as well?!) And what's the difference between eibnetserver and eibnetipserver?

Do you think we can find better names? Or do you like them and know the differences by heart?

[Matthias Urlichs]

On 20.01.2017 17:11, Thomas Dallmair wrote:
> Do you think we can find better names?

We should. Ideas welcome.

The problem with "KNXnet/IP" is that there are four possible options
(tunnel or multicast, client or server) and that label can apply to any
and all of these.

--
-- Matthias Urlichs

[Thomas Dallmair]

You mean something along the lines of

• --enable-tunnelingclient
• --enable-tunnelingserver
• --enable-routingclient
• --enable-routingserver

?

[Richard Hartmann]

If you mean routing == multicast, then please call it "multicast", instead.

Richard