> > > Assuming your client-side processing is optimized as possible (i.e. > you're using the browser to parse the XML). > > Are you converting the XML to HTML? If so, perform the conversion on the > server and send the generated HTML to the client. Manipulate the DOM on > the client. GWT excels at that work, as it is designed to reduce > DOM-related memory leaks. > Hi, I am getting the data from server as xml.toString() and using com.google.gwt.xml.client.XMLParser to convert it to Document at client side, com.google.gwt.xml.client.Document temp = XMLParser.*parse*(iMessage) this part doesnt bother me actually, the part which bothers me is after this;
During searching and processing of this Document, depending on the loop size ( node depth and node size ) the browser locks, ( in background GWT uses JS,normally in JS when we shred the data these locks and browser waitings dissapears), in GWT what should i do ? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
