FYI because some people might not be on webkit-dev. BUT if this seems even remotely interesting to you, get on that list! (They recently split it into webkit-dev and webkit-help, so signal to noise should get better than it was before...in case that was a concern of yours.)
J ---------- Forwarded message ---------- From: Adam Barth <aba...@webkit.org> Date: Fri, Jul 3, 2009 at 12:23 PM Subject: [webkit-dev] [V8] It's time for V8Proxy to come to Jesus To: webkit-...@lists.webkit.org Cc: Mike Belshe <mbel...@google.com> If you're uninterested in the V8 bindings, you can skip this email. Clocking in at 3255 lines (plus a 682-line header file), V8Proxy is out of control. Historically a bridge from the V8 bindings to the V8 engine, V8Proxy is responsible for a number of tasks including: 1) Creating new contexts 2) Implementing security checks 3) Supervising garbage collection 4) Caching event listeners 5) Executing scripts 6) Converting between frames, contexts, and global objects 7) Manging DOM wrappers 8) etc, etc, etc I propose we separate these concerns into a number of distinct classes that have clear, understandable purposes before things get worse. Please let me know if you have any in-progress patches to V8Proxy. I'd like to lock that file sometime next week while I rip it apart and put it back together. Thanks, Adam P.S., FrameLoader: you've escaped for now, but don't think I'm not watching you. _______________________________________________ webkit-dev mailing list webkit-...@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
