Maybe too late, but I found that you have to do the following :
- create a directory struts under your Webroot directory
- copy all contents from the static directory into this struts directory
- copy the entire contents of template directory into this same struts
directory, without the template
Jason Wyatt on 27/07/07 08:55, wrote:
I've been trying to speed up the Ajax performance of our application, based
on the notes at http://cwiki.apache.org/WW/performance-tuning.html
I'm a bit unsure where I should extract the static content to, such as the
css and javascript files included by
Hi,
we also had the similar problem, we had a s1.x application with dojo and
we did all the performance enhancements that was recommended by dojo,
but we could not achive what we want and our application was running in
https mode. it add more performance problem to the application.
Thanks,
I have a very complex app using Dojo that just went live a few weeks ago
(although *not* using S2), and this past week we got a 70+% performance
improvement out of it. We did three things Dojo-related. First, we
used a custom build (previously we just let Dojo import whatever it
needed on
or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Frank W. Zammetti [EMAIL PROTECTED]
To: Struts Users Mailing List user@struts.apache.org
Sent: Saturday, July 28, 2007 10:17 AM
Subject: Re: [S2] Ajax performance optimisation
I have
Hi Frank,
First of all thanks for these tips.., we did the custom dojo build and
parseWidget tag setting also. but we havent done the 2nd and 3rd tips
you have given here., i have a small doubt when it comes to moving
static resource to the web server. will there be any problem when it
comes
Nuwan Chandrasoma wrote:
Hi Frank,
First of all thanks for these tips.., we did the custom dojo build
For anyone reading, this is an especially important tip if your app is
being access on a WAN or public Internet. Our app is a backoffice app,
but we have a lot of people coming in over
Martin Gainty wrote:
Hi Frank-
My apologies for jumping in the middle of a thread
No need to apologize, I did the same thing! LOL
-could you elaborate on what you used for a 'custom build'?
Yes... Dojo supports the ability to create a custom build, where you get
a dojo.js file out that
Frank W. Zammetti on 28/07/07 16:10, wrote:
Martin Gainty wrote:
-where you able to collect metrics for scenarios other than expire
headers of 1 hour..perhaps 2 hours?
No, we debated various times but settled on one hour because that seemed
a reasonable period of time to account for JS
In our case, it's not the initial load that was killing us... well, it
*was* a little too long (and we have a very nice Please Wait with
spinning gears and such during that period)... the problem is the
underlying requirements for the application. Let me try and give a
brief background
Sounds like a whole portal - quite a broad scope for a webapp. I guess you are
using iframes so that you can flow each iframe thro further requests without
losing the state in the other iframes or the main page. The app that I'm working
on has several different tabs, but all within a single
11 matches
Mail list logo
