Hi Oleg, Andrea is right there is a cost/benefit to caching and it's not a magic cure-all for selector engine performance. NWMatcher uses result caching only when it recognizes the benefit is greater than the cost. For example NWMatcher only caches when mutation events are supported, querySelectorAll is buggy or not supported, and the cache initialization isn't being called aggressively. Result caching should be seen as one part of an overall engine just as result chaining, $().foo().bar().bang(), is one part of a framework. If abused or used incorrectly both can be seen as "bad practices", but under responsible use they cause no measurable performance loss.
- John-David Dalton --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
