Hi Thanks for your answer. I found some of these options yesterday and tried to set them with by a javascript "onload" tag for the html page. Especially setting "parseContent" to 'false' gives an significant speedup, unfortunately this breaks all links with 'theme="ajax"' (or converts them to "normal" links). But... The rendering performance was still to bad and did not solve the "double request on page load" behaviour bug. The solution I came to was to use the "handler" attribute and to load the content by XMLHttp request. This loads the page in less than a second (compared to ca. half a minute). The links are of course still broken.
Although I think this 'remote div' feature is very interesting, I don't think it is usable for "real" or more complex applications in this state of developing... At least the documentation should have a notice of this. Sebastian Josef Adamčík schrieb: > On 8/10/07, Sebastian Kolbe <[EMAIL PROTECTED]> wrote: > >> An other problem for me is that most browsers are rendering >> very, very slow into such a 'div'. A page with tables that normally >> (normal struts-action rendering into a browser window) takes less >> than 1 second needs here almost 20 - 30 seconds. It looks like the >> javascript in browser is doing some sort of postprocessing on the >> content? >> > > I have noticed similiar behaviour. Struts uses component derived from > dojo's content pane. Look at > http://dojotoolkit.org/book/dojo-book-0-4/part-4-more-widgets/advanced-contentpane-usage > - interesting is FAQ at the bottom of the page and question: "Why is > ContentPane so slow? ". > > Cite from answer: > "You probaly send it a big chunk of html with deeply nested tags. > - Send it a html fragment, not a complete page with doctype and everything > - Try to make the HTML simpler and use css for styling > - Turn off the options you dont need: adjustPaths, extractContent, > executeScripts, parseContent" ... > > (the answer continues on the page, but i'll foucs last quoted point) > Struts div has parseContent option turned on in default (it allows > dojo to create other dojo components in parsed html). When i tried to > turn it of, speed of page rendering raised rapidly. > > But there's a problem: struts div tag doesn't support this option. > One solution is direct construction of dojo sceleton for conent pane. > E.g: > <div dojoType="struts:BindDiv" .... parseContent="false"> > But remeber, you'll lose ability to include all struts tags which are > based on dojo in the loaded output. > > p. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
