To abstract or not to abstract? That is the question

[squarooticus]

Selection property querying is better than it was, but querying still feels odd:

• Using "has been applied" to mean "on" or "in use" or "active" necessitates a bunch of explanatory text in §5.2 that would otherwise be unnecessary.

• Reporting "true" for properties that are "on" or "in use" or "active" is very UNIX-y, but less abstract than I'd like to see here. At least we're not encoding -1 as a special return value anymore. A perhaps suitably abstract interface here would be something like:

tp := Connection.GetTransportProperties()
if tp.has('reliability'): ...

[mwelzl]

Welcome, author!

[squarooticus]

Ugh. Can I insert a GIF of a pile of books falling on me?

[tfpauly]

Also, make SecurityParameters more abstract (don't do "strings" that look like Python).

[squarooticus]

Also, make SecurityParameters more abstract (don't do "strings" that look like Python).

I made a change in the third commit of #658. LMK if that matches your expectations.

[squarooticus]

Er, I mean #687. @tfpauly