On Tue, May 26, 2009 at 9:42 PM, Maciej Stachowiak <m...@apple.com> wrote:
> > On May 26, 2009, at 7:00 PM, John Abd-El-Malek wrote: > > >> This will work fine for appcache and localstorage, but isn't sufficient >> for workers since the same caller gets different objects depending on which >> process this is running in. This doesn't happen for appcache and >> localstorage. >> >> > It's fine to use virtual methods when you actually need runtime > polymorphism at the same call site. The point is not to tie yourself in a > knot if there really is true polymorphism, just to avoid paying runtime > penalties for anything that can actually be a compile-time decision. If it > can't be, then so be it. Sounds good. I was a bit worried that we were needlessly adding a lot of complexity to the code, but you're definitely right that slow performance can be a "death by a thousand cuts" type thing. I'll give it a shot for DOM Storage, but it sounds like workers will need to still use polymorphism.
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
