Good point, I should make it clear that "user class object" does not include objects that extend JavaScriptObject.
On Fri, Sep 5, 2008 at 1:31 PM, John Tamplin <[EMAIL PROTECTED]> wrote: > On Fri, Sep 5, 2008 at 1:14 PM, Emily Crutcher <[EMAIL PROTECTED]> wrote: > >> I don't think it's one-to-one comparable with either identity or normal >> equality maps, as the definition of when two keys are equal will solely rely >> on the underlying JavaScript interpretation of the keys, and that will be >> done using the fastest semantics we can get. So for strings it is equality >> based, as that is how the underlying JavaScript API treats their strings, >> but for user class objects it will be identity based, as the fastest way for >> us to index them is via a extended property added to the object. >> > > Note that you can't add properties to some JSOs, so if you rely on that > some objects can't be stored in these maps. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > > -- "There are only 10 types of people in the world: Those who understand binary, and those who don't" --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
