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) many people can avoid their own implementation of object release algorithm used to classify the significant (regular) and not significant (which do not require object existance at all) object references.
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. > > If you need to release objects on the client side, it is best to do so by > hand when they are no > longer in use. If you need to also tell the server to release them, use an > RPC call of some sort, > and have the server release the data when the session expires (if you are not > actually storing the > data in the session). > > > > Garo.Garabedyan wrote: > >http://garabedyan.wordpress.com/2008/11/18/javalangref-in-googlewebto... > > > Is java.lang.ref.* functioning in GWT? I come to an idea that > > java.lang.ref.* is necessary to enable proper garbage collection while > > implementing the Observer pattern in Model View Controller.- Hide quoted > > text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
