> > What about the case of multiple instances of the same module?
We talked about it offline and decided that the fix covers 99.9% of use cases. Kelly said that the bootstrap process wouldn't handle loading two modules with the same name anyway. The other concern is that we might have modules compiled with different versions of GWT, which can cause trouble if we change the implementation later. createUniqueId() guarantees a unique id for the document, but makes no > guarantees about uniqueness within the global namespace ($wnd). I think it > would be a worthwhile addition to create such a method in the future, > though. And to that point, we are generating a unique name for the hidden iframe, not a unique ID. I'm not sure what effect it would have to have names that are not unique in the global namespace. Thanks, John LaBanca [email protected] On Thu, Jan 7, 2010 at 9:24 AM, Joel Webber <[email protected]> wrote: > createUniqueId() guarantees a unique id for the document, but makes no > guarantees about uniqueness within the global namespace ($wnd). I think it > would be a worthwhile addition to create such a method in the future, > though. > > On Thu, Jan 7, 2010 at 4:12 AM, Thomas Broyer <[email protected]> wrote: > >> >> >> On Jan 7, 12:23 am, John Tamplin <[email protected]> wrote: >> > >> > What about the case of multiple instances of the same module? >> >> How about simply using Document.get().createUniqueId() ? >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors >> > > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors >
-- http://groups.google.com/group/Google-Web-Toolkit-Contributors
