[squid-dev] RFC Sourcelayout for clientStreams
Amos Jeffries
squid3 at treenet.co.nz
Mon Jan 9 07:21:11 UTC 2017
I've been looking at the clientStreams objects and moving them to a
library for the SourceLayout project.
What I would like feedback on before I go and make a namespace and
library up is whether we want to retain the term "Client Streams" as the
name for that component or whether there is a better name?
* Maybe 'Body' from the BodyProducer/Consumer objects which are the two
main endpoints of a clientstream so far.
* Maybe 'DataFlow' from the idea that it is for handling opaque data,
and also the HTTP/2 frame name for the bytes transferred this way is DATA.
Any other ideas or keep ClientStreams?
Amos
More information about the squid-dev
mailing list