Hooking the cleanups to the connection pool may be a little too late for some modules (Example SSL shutdown/SSL Alert). For filters like SSL, the EOC logic would probably be just fine - I can't think of other filters which cannot use the EOC logic.
Correct. A cleanup is too late for this particular action.
I'd like to understand what's the inhibition/limitation for adding a new hook - IOW, why are buckets like EOC preferable over a finish_connection hook ? I can guess it's something to do with the performance - but a detailed explaination/pointer to something would be helpful.
It's that EOC is the proper parallel to the EOS bucket. We just never realized we needed it. ;-) But, I'm fairly sure that it is the 'right' solution here.
Also, I'm not sure that we can add a new hook to 2.0; so if we added a hook to solve this problem, it'd have to wait for 2.2 to be resolved. (We might be able to add it to 2.0, but I'm not 100% sure.) -- justin
