It looks to me like its about the use of private assets. If you look at the source, you'll see stylesheets and images being referenced with Tapestry URLs like "...?service=asset&sp=......................".
IE is more liberal about caching assets like this. Navigator is more paranoid ... it will keep requesting them every cycle. To even things out and improve overall performance, follow the instructions in the guide about externalizing private assets. Basically, you configure things so that Tapestry can copy private assets to a file system directory mapped to a URI in your web server, then URLs for the assets are static. There may be a bug in here though; I need to see if I can write the correct date headers to address Navigator's caching approach. ----- Original Message ----- From: "Ivanhoe Abrahams" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 10, 2002 2:37 AM Subject: [Tapestry-developer] Performance difference between IE, Netscape, Mozilla > Hi guys > > While the project I'm working on is still far from finished, I just thought > I'll check compatibility across > IE, Netscape & Mozilla. > > Although the HTML is fine I do notice a performance difference between IE on > the one hand > and Netscape + Mozilla on the other hand. > > Just using the output on the bottom of each page eg. "<!-- Render time: ~ > 190 ms -->" I noticed > that the same page renders in 190 ms in IE but consistently will render in > about 270 - 290 ms > in Netscap and Mozilla. > > I also noticed that the console output in the JBoss server console > outputs the following when receiving a Netscap/Mozilla hit on said page > > ***Netscap/Mozilla hit**** > >>09:26:17,964 INFO [AbstractEngine] Begin service /courier/courierprices > >>09:26:18,214 INFO [AbstractEngine] End service > >>09:26:18,344 INFO [AbstractEngine] Begin service /courier/courierprices > >>09:26:18,374 INFO [AbstractEngine] Begin service /courier/courierprices > >>09:26:18,374 INFO [AbstractEngine] Begin service /courier/courierprices > >>09:26:18,374 INFO [AbstractEngine] Begin service /courier/courierprices > >>09:26:18,435 INFO [AbstractEngine] End service > >>09:26:18,525 INFO [AbstractEngine] End service > >>09:26:18,655 INFO [AbstractEngine] End service > >>09:26:18,755 INFO [AbstractEngine] Begin service /courier/courierprices > >>09:26:18,765 INFO [AbstractEngine] Begin service /courier/courierprices > >>09:26:18,805 INFO [AbstractEngine] End service > >>09:26:18,895 INFO [AbstractEngine] End service > >>09:26:18,925 INFO [AbstractEngine] End service > > and when receiving a IE hit on said page > > ***IE hit**** > >>09:28:02,524 INFO [AbstractEngine] Begin service /courier/courierprices > >>09:28:02,695 INFO [AbstractEngine] End service > > From my point of view it seems like the server is doing much more to field a > Netscape/Mozilla connection > > PS. This is not that important as I suspect that most users will be on IE > anyway. Nevertheless > I would like to understand this difference. I dont like IE winning this one > by that far. > > > Thanx in advance > > Ivanhoe Abrahams > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.423 / Virus Database: 238 - Release Date: 2002/11/25 > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
