Jim Jagielski wrote:
On Dec 8, 2005, at 11:13 PM, Roy T. Fielding wrote:
I would extend the EOS bucket data to be an errno and then have
mod_cache check for that data != 0 when it does its EOS check.
Ugh, EOS means exactly what it says...
No, but we can graft it onto the currently unused EOS bucket data.
There's really no need to refactor...
Hmmm... or use the error bucket type, with some intelligent
checking at the correct time.
++1. We have the technology, we don't need to extend EOS buckets.
If anything gets in the way of the error bucket making it to the right
place, that behavior would be a bug.
Bill
