3 ms·
Most of it is that it's harder to come up with useful, safe, not overfitting APIs the deeper you go into internals. For example, registering extensions is rarel
by FiloSottile 8y ago
Most of it is that it's harder to come up with useful, safe, not overfitting APIs the deeper you go into internals. For example, registering extensions is rarely useful on its own as extensions are allowed to change literally anything else in the protocol, and without hooks for everything else you did not get much value.
But! Hearing about what people would like to do and then putting together an API if it makes sense is my job! So please do open an issue saying what you'd like to do but can't.
For example, I mean to extract Client Hello parsing and a capturing middleware net.Conn, as a lot of passive things can be implemented that way.
- kodablah 8y agoMy use case recently was [0]. I might open an issue if that spec comes further along. > I mean to extract Client Hello parsing Something like that could have helped when I was toying w/ DTLS, though [1] did a great job on their impl. 0 - https://tools.ietf.org/html/draft-krawczyk-cfrg-opaque-01#section-4 https://tools.ietf.org/html/draft-krawczyk-cfrg-opaque-01#se... 1 - https://github.com/pions/dtls https://github.com/pions/dtls