After 2.2.0 was released I changed mod_rivet so that a single channel was created per each child process.

In the recent thread about headers redirection Damon recalled the fact Rivet channel is fully a Tcl channel and as such you can call fconfigure on it to change the buffer size

I don't see scenarios where Rivet will be deployed in large systems where many totally independent programmers will be developing entirely unrelated applications stretching or shrinking the channel buffer size, but we should be sound about it and at least reestablish a way to have optionally separate channels when separate interpreters are used for different virtual hosts. For most cases having a single channel controlled by a single programmer or team of programmers can be an optimization worth to keep.

Doing it for code in branches/2.2 means I have to partially revert to the code in 2.2.0. The code in trunk is probably easily manageable as threads have their interpreters private descriptors and a channel pointer can be stored in there on a per interpreter basis instead of a per thread basis

I'd like to work on this starting with January and when successful I would release branches/2.2 as 2.2.1

 -- Massimo

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to