On Nov 1, 2005, at 2:57 PM, Katie Capps Parlante wrote:
I said: take the discussion to the list, because Bryan's writeup is
informative and the ensuing conversation will help me get more
information to make a good judement. ;)
It sounds like per item notification is something we should do in
the long term -- at least in 0.7.
I agree with this point.
I'm taking Ted's comment seriously that tweaking this in 0.6 is a
bit risky. Ted: is that just a guess at this point? Is it worth
going down the path of implementing it to see if it really pans out
as risky? Could we allocate real time to functional tests to
mitigate the risk?
I'm certainly willing to try implementing and see how risky it
looks. I just want us all to have the same expectations about the
nature and possible impact of a fix.
Allocating time to functional tests would have benefit that is
multiplied for all developers, since there's always the risk of
unexpected side-effects from a fix.
I'm also interested in whether or not we know that the current
monitor implementation is impacting performance as suspected. Is
this showing up in any of our performance use cases?
I haven't noticed the monitor code at the top of the profiles that I
did but I haven't done any profiles in a about a week.
Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
