Hi Taco,

My 2 cents on this matter is to use IIS or Apache or whetever  
webserver you are using and properly set content expiration headers  
on everything that is static, e.g. your .css files, any images you  
are loading, and javascript. On our site, it's 12 hours for the  
images, css, and and js files.

Forget about trying to set expiration times on dynamic pages  
especially if there are going to be parameters in the querystring. It  
just won't work reliably. Instead, invest in ZipEnable or gzip or  
other HTTP compression software to reduce the html filesize of the  
content you are delivering.

If instead you are trying to reduce the number of hits to a database  
or server load - which probably would be a concern for 95,000 request  
a day, you'll need to tweak the Database Caching settings of  
Coldfusion Administrator and/or look into a page caching tag such as  
CF_Accelerate.

If you need to improve user waiting time, consider that the visitors  
upload bandwidth is most likely one the more limiting factors, and  
the best way to address this is to reduce the number of cookies you  
are setting. More info on this topic can be found at:

http://www.die.net/musings/page_load_time/

Regards,
Joris


On 26/08/2007, at 7:03 PM, Andrew Scott wrote:

> Taco,
>
> That seems to be a very slow way of refactoring to your final  
> solution.
>
>
>
> On 8/26/07, Taco Fleur <[EMAIL PROTECTED]> wrote:
> Because at this stage that would complicate matters.
>
> Our policy is:
> - first make it work without JS
> - add some JS to enhance user experience
> - add AJAX to improve user experience
>
> Let's focus at the job at hand for now. I've decided (until a  
> better solution comes along)
> to use history.length > 1 instead of history.length > 0
> and only miss out on a few requests
>
>
> On 8/26/07, Steve Onnis < [EMAIL PROTECTED]> wrote:
> So why not look at AJAX then?
>
> From: cfaussie@googlegroups.com [mailto: [EMAIL PROTECTED]  
> On Behalf Of Taco Fleur
> Sent: Sunday, 26 August 2007 6:13 PM
> To: cfaussie@googlegroups.com
> Subject: [cfaussie] Re: bloody browsers ;-)
>
>
> Steve,
>
> let's see, lets just take 5,000 as a random number of users per  
> day, since we're talking about a search engine www.clickfind.com.au
> Let's say they all perform one search, each search returning 20  
> results on one page, the user will look at each listing and return  
> to the search results by other means than the back button and thus  
> refreshing the page and making another request each time.
>
> I would say that's 95,000 requests that could have been handled by  
> displaying the page from the cache. Now let's say that each request  
> is about 15KB = 1425000KB saved on a daily basis. I;m not that  
> great with numbers, but I think that's 1425MB a day which is quite  
> significant.
>
> Not only does it save bandwidth, but also database processing and  
> user waiting time, I think this is a very strong case.
>
>
>
> On 8/26/07, Steve Onnis < [EMAIL PROTECTED] > wrote:
> Taco
>
> How much bandwidth are you hoping to save by doing this? I would  
> say the savings by implementing something like this would be  
> minimal compared to the effort you would you have to go through to  
> make it work properly
>
> From: cfaussie@googlegroups.com [mailto: [EMAIL PROTECTED]  
> On Behalf Of Taco Fleur
> Sent: Sunday, 26 August 2007 5:28 PM
> To: cfaussie@googlegroups.com
> Subject: [cfaussie] bloody browsers ;-)
>
>
> Hi all,
>
> I'm trying to save some bandwidth in an app and implement some  
> javascript back buttons, so that we're using the browsers history  
> instead of calling the page again. I'm finding it to become a bit  
> of a nightmare.
>
> At first I had a problem where someone could open up a new browser  
> and paste the URL in it, thus history.back() not working, then I  
> checked for the history.length and made sure there was some history  
> to go back to, but if you have google.com as your homepage that  
> loads all the time in a new browser, then there is some history,  
> but not a page you want to go back to.
> Then I thought of
> <cfif refindNoCase( "^https?://(www|development|testing|staging) 
> \.myproject\.com\.au", cgi.http_referer ) > onclick="alert 
> (history.length);if ( history.length > 0 ) { history.back(); return  
> false }"</cfif>
> i.e. making sure the referring page was on the same domain, but now  
> FireFox doesn't want to play, it reports 1 for history.length while  
> nothing was loaded yet!
> Then I thought of using a browser sniffer and adjust for FireFox,  
> but I don't want to go down that path as I know it will be a never  
> ending one.
>
> Before I abandon this idea and hope people will use the browser  
> back button, is there someone who knows a fix for this?
>
> Thanks in advance.
>
> -- 
> *** http://www.clickfind.com.au
> The new Australian search engine for businesses, products and services
> *** http://brisbane-web-design.pacificfox.com.au blog
> *** Virtual and Dedicated Servers with MS SQL from $250 a month
> *** Virtual and Dedicated Servers with registered version of  
> ColdFusion from $350 a month
> *** ColdFusion licenses at the lowest price
>
>
> *** http://brisbane-web-design.pacificfox.com.au blog
> *** Virtual and Dedicated Servers with MS SQL from $250 a month
> *** Virtual and Dedicated Servers with registered version of  
> ColdFusion from $350 a month
> *** ColdFusion licenses at the lowest price
>
> The new Australian search engine for businesses, products and services
> *** http://brisbane-web-design.pacificfox.com.au blog
> *** Virtual and Dedicated Servers with MS SQL from $250 a month
> *** Virtual and Dedicated Servers with registered version of  
> ColdFusion from $350 a month
> *** ColdFusion licenses at the lowest price
>
> -- 
>
>
>
> Senior Coldfusion Developer
> Aegeon Pty. Ltd.
> www.aegeon.com.au
> Phone: +613  8676 4223
> Mobile: 0404 998 273
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to