On Thursday, January 10, 2013 7:49:37 AM UTC-2, Jens wrote: > > Just out of interest: Why does a large server side lazy collection forces > you to use a synchronous XMLHttpRequest that will noticeably block your > whole browser while the server does its work?
This application has a complex graph of objects, when a collection of objects is loaded, it crashes browser due memory constrains. > > Gilead will set not yet loaded lazy properties to null so instead of using > Gilead you could also create a DTO class with only the information you need > and then fill it on the server without ever touching the lazy properties. > Good to know, I've not lost time using Gilead. Using DTO will force me to change hundred of UI widgets, which I don't have anought time to do now. Thanks, Edson > -- J. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Vi8wPnEJXMAJ. 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.
