Issac, Do you have a count of cases where the current behavior is causing problems? Can you estimate the % of high-demand sites which have problems?
You *cannot* discover the range and severity of problems a proposed change may cause by describing it on a mailing list! The only way to find out is by releasing code. (This is a law of software.) The way most established software shops address problems where different behavior is required is to implement it under a new API. IF the current behavior causes problems which sites cannot readily detect, or is triggered by third-party software which they cannot fix, then you must consider implementing the new behavior under the same API. Arguably, if they cannot detect it, it's not an issue for them. In any case, SEMANTICS MATTER, and it's clear that the current API is not ideal for either behavior. This means it should be DEPRECATED. Since this is a pressing problem affecting major sites, I suggest you implement the new behavior under a new API in 0.7, ASAP.
