| Author | Messages | |
Rodney
Posts:77
| | 10/06/2006 4:18 AM |
| Hi John,
I decided to try PageBlaster (gotta support homegrown DNN ;) so I removed Blowery and installed PB.
I then noticed some odd caching problems- like half the screen would be rendered and the rest not (and this was the page in the cache, so I was stuck with half a page until I removed PB).
I tried it on PokerDIY.com - Has anyone else reported problems with it? I scanned the Forums and nobody seemed to mention it (you would know if you had this - it renders the site unusable, literally)
I'm really keen to try it again but I thought I would check here first...
One more thing - on a lot of modules I can't use caching as it breaks them (mostly where you have to load dynamic content based on userID) - what happens with the cached page? Eg. on the home page there is a "My Profile", and then someone else requests the home page and they get served up the cached page with my UserProfile?
Thanks
Rodney
Smart-Thinker.com
| |
thanks
Rodney Joyce
Smart-Thinker.com - DotNetNuke Modules for Social Networks
PokerDIY.com - Simple Poker Leagues | |
| |
| John Mitchell
Posts:3033
| | 10/06/2006 8:01 AM |
| Hi Rodney,
No, I haven't seen or heard of that problem before. To refresh a cached page you can hold CTRL and then Refresh or (CTRL+F5), and PageBlaster will clear and reload it's cache.
PageBlaster only caches pages for anonymous users to avoid caching any user specific information. Compression still works when logged in, but the pages are not cached. | | | |
| Rodney
Posts:77
| | 10/06/2006 8:25 AM |
| Ok - I will give it another try and attempt to work out where the problem is...
I'm trying to understand this caching - it does seem to mean that I loose caching control at module level for unauth. users? So for example if I display a banner advert for 2 minutes and a quote for a minute and a random profile (not cached - so refreshes on each page view - for all users) - then with PB this would all cache for the duration of the overall cache - hence all users would see the same thing for al page views on that page until that cache expired? This is not neccessarily a bad thing, but these are real examples I am using - is that an accurate analysis? | |
thanks
Rodney Joyce
Smart-Thinker.com - DotNetNuke Modules for Social Networks
PokerDIY.com - Simple Poker Leagues | |
| John Mitchell
Posts:3033
| | 10/06/2006 9:35 AM |
| One other thing that may help is to make sure that the declaration for the PageBlaster in your web.config is the very first one in the httpModules section.
Yes, your analysis is correct. You can think of it as saving the page off to a static html page. Of course this is very good for a page that does not change much, but like you said, maybe not so good on a page that changes very often.
The trick is in invalidating the cache when the page does change, so that a fresh copy can be cached again automatically on the next request.
PageBlaster does cache invalidation whenever a post-back is made to a page and a user is logged in. So if you decide to update a page, you will be able to see your changes right away.
Also, if you are interested in more granular control per page, PageBlaster Pro will be out soon. It has a module that you can place on a page to control the cache times individually, along with some other page manipultion strategies like Virtual page names, and replacements. | | | |
| Michael van Zwieten
Posts:2
| | 10/10/2006 10:30 PM |
| | Hi all... I'd like to chime in and say that I've been experiencing some weird caching issues since I've been running Pageblaster. For instance, I'm seeing weird issues when making a change through my host account to a page, but then after logging out, that change doesn't take effect when browsing to it as an anonymous user... at least not immediately -- but at a much later time. I've tried putting the declaration first in the web.config, I've tried CTRL+F5 while logged in as host, or as anonymous... no difference. At some time later... could be hours, or the next day, when browsing to it, I'll find that the change has taken place and the page has finally been cached. I just recently noticed this when I chose a logo for my site, but then went back to alter it and sent up a new image. For approximately 1 day, my pages were all referring to an image that no longer existed and were showing a red X. Just now, I changed one of my page menu dropdowns to be disabled so that people can't click on it to be presented with a blank page... It works fine looking at it as host... but anonymous still sees the old page where people would click on the menu item and be presented with a blank page. Does anyone know what it would take to immediately cache a page so that it's reflected on the anonymous users' end? Thanks in advance for your help and advice... BTW, I'm running the latest version... 1.4.1... ;) | | | |
| John Mitchell
Posts:3033
| | 10/11/2006 7:18 AM |
| Hi,
It sounds like some of the issues you are having is because of changes that happen on multiple pages. If you change anything on the menu, or the logo, then this is something that makes all pages invalid, so all the cache needs to be cleared. Pressing CTRL and refreshing should build a new cached page for a specific page even when not logged in, so I'd like to see your site to understand why it may not be working.
To clear all of your cache with version 1.4.1 you will need to remove all the disk files, and restart your application. You can make your application restart by uploading a copy of your web.config or making a small change to it online.
| | | |
| Michael van Zwieten
Posts:2
| | 10/17/2006 9:08 PM |
| | Hey John... I'd be glad to work with you on this... Please let me know how you'd like to handle getting on my site(s)... If you could, please send me a personal email, and we'll work it out. Thanks in advance! | | | |
|
|