Andy, this last recommendation is at odd with your first statement.
I agree we should look for performance gains in other places. But we should do that too, not instead. 20% is such a large number that we ought to address this first.
I think I stated it poorly. What I meant was that I don't think we can change this safely, as per the concerns I detailed in my other posts. Therefore, I think we're going to end up having to improve other areas in other to make up the lost performance.
I personally like Elena's first proposal, to pass null. I think it's simple and while I agree it *may* cause some disruption the gain is such that it makes it worthwhile. Think about the number of people/users who will benefit from it vs the number of component developers who will have to update their components...
Yes, but I don't know if it will ultimately work.
-- Andy Clark * [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
