On Wed, Nov 19, 2008 at 5:44 AM, Garo.Garabedyan <[EMAIL PROTECTED]> wrote: > I think that by implementing java.lang.ref.* in the client side > (translating to written by hand JavaScript code that adds and can > manages new type of object references)
I sincerely doubt that is even possible, because: > On Nov 18, 2:27 pm, Jason Morris <[EMAIL PROTECTED]> wrote: >> You can't use java.lang.ref on the client side, because JavaScript has no >> notion of weak, soft, or >> phantom references. You can however use the java.lang.ref package on the >> server. The java.lang.ref.* classes work intimately with the JVM to give the user some insight into the memory management cycle. The Javascript "VM" doesn't allow that insight because there's no API for it. Someone with more theoretical background can correct me if I'm wrong, but I'm pretty sure the only way to implement java.lang.ref.* in the browser is to emulate a JVM in Javascript and run GWT on top of that. That would be an enormous undertaking and it would require rearchitecting and rewriting all of the client side infrastructure. In other words, I feel pretty safe saying "it ain't gonna happen". Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
