I think beestings change the html every time.
this means html is not able to be cached.
am I right?
A:
I assume that by beesting, you mean some sort of random number in the URL.
Yes this will (usually) stop caching of pages. Some browser may still cache some or all of the page.
As to whether not to avoid it. Would caching a page stop it working as it should? If your page has fairly random content or content the changes often, users would not see this if the page is cached.
If you can avoid the need to stop caching, pages will be able to load faster. Which makes for a happy user.
thecoshman
2010-03-26 13:13:10
I so totally do know how to spell... see, if I deny it hard enough others will think it is them who is wrong. Thanks Raj!
thecoshman
2010-03-26 13:22:11
OK then is it better to divide .js file , two part? I mean one part is .js using beestings, and another part is .js not using beestings. I think the second .js file can be cached
sunglim
2010-03-26 13:36:38
Well yes you could do it that way. Bear in mind though that there is overhead to downloading a second JS file. you may be better of just putting all the code into the one and 'trimming the fat'. Do you really need to give the user different JavaScript code for each page though?
thecoshman
2010-03-26 13:53:26