Re: [quicwg/base-drafts] create codec streams only when necessary (#2090)

[Martin Thomson <[e-mail]>]

Let me try to expand on my earlier comment.  I currently create these streams when building my connection object.  This allows requests and responses to use those streams directly.  If the streams might not exist, then I have to allow those values to be absent throughout, which is annoying but not a big deal.  More of a concern is that this is concurrent code, so deferring creation would mean that I would have to guard the variables holding the streams with a mutex (or atomic, which always gives me the creeps).  That creates the potential for contention point on every new message.

Not saying impossible, but it is annoying.  And all in service to implementations that are not interested in handling a stream that will only ever contain a single octet.  Given the complexity of this protocol as a whole, it seems like a strange optimization to make.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2090#issuecomment-446468738