2000

It keeps the original formatting. numero = 33863
interpreted = N
texte = Ever since I first reported my difficulties with the template cachingproblem, I have been trying to figure out what the pattern is. While Iam still not absolutely sure, I have compiled other tidbits of info thatmight help, but I am not sure. It may, in fact, be related to thebrowser's cache and not WebStar's. Netscape does support thesuper-reload feature, but when Netscape 4 came out, it appears to havelost its ability to super reload (or even regular-reload) an individualframe. This is where I first noriced the problem, and where it wascausing me the most grief - in a framed webpage. I assume that when Isuper reload a frame in Netscape, that it does not necessarily superreload the individual pages in that frame? I found that I would try tosuper reload the entire frame set, that the same data would display - soI would flush WebStar's cache, and the data would change. But, I alsofound that if I told the offending frame to open in a new window, superreloaded that window, close that window, then refresh the entire frame,that the new data would be displayed.I did put into one of the pages that was causing problems, the no cachemime headers that was requested that I add. Originally, I did not thinkthat the problem was solved, because I did not notice any change inNetscape. However, I wanted to check out the routine in the samebrowser that my customer uses (IE 4 for Windows), and found that theproblem was not ocurring there. Later, when trying Netscape again, itdoes seem to stop the problem there as well.I hope that this info might be of some help. This problem is causingsome nasty side effects. Normally, after making a purchase, if I wouldreturn to thehome page of that site, I would automatically have a new cart generated(as long as the link did not pass the old cart number). Now, aftermaking a purchase, if I return to the home page of the site, I can goall the way through the routines, including what appears to be addingthe same item to the cart as before, only to find out that I am on acached page, and none of it really happened. This also causes problemswith a WebMerchant page that I am using. After someone makes a purchaseon my customer's site, I simply use a meta refresh tag to keep recyclingthe page until the approval is processed, and the WebMerchant approvedpage is written to disk. Then, I change the refresh interval to 0, andchange the redirect location to take the customer to that written page.Now, however, that page just keeps going in a circle, even aftertheWebMerchant page is written.Thanks,Dennis#############################################################This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to Associated Messages, from the most recent to the oldest:

More on the template cache problem... (Dennis J. Bonsall, Jr. 2000)

Ever since I first reported my difficulties with the template cachingproblem, I have been trying to figure out what the pattern is. While Iam still not absolutely sure, I have compiled other tidbits of info thatmight help, but I am not sure. It may, in fact, be related to thebrowser's cache and not WebStar's. Netscape does support thesuper-reload feature, but when Netscape 4 came out, it appears to havelost its ability to super reload (or even regular-reload) an individualframe. This is where I first noriced the problem, and where it wascausing me the most grief - in a framed webpage. I assume that when Isuper reload a frame in Netscape, that it does not necessarily superreload the individual pages in that frame? I found that I would try tosuper reload the entire frame set, that the same data would display - soI would flush WebStar's cache, and the data would change. But, I alsofound that if I told the offending frame to open in a new window, superreloaded that window, close that window, then refresh the entire frame,that the new data would be displayed.I did put into one of the pages that was causing problems, the no cachemime headers that was requested that I add. Originally, I did not thinkthat the problem was solved, because I did not notice any change inNetscape. However, I wanted to check out the routine in the samebrowser that my customer uses (IE 4 for Windows), and found that theproblem was not ocurring there. Later, when trying Netscape again, itdoes seem to stop the problem there as well.I hope that this info might be of some help. This problem is causingsome nasty side effects. Normally, after making a purchase, if I wouldreturn to thehome page of that site, I would automatically have a new cart generated(as long as the link did not pass the old cart number). Now, aftermaking a purchase, if I return to the home page of the site, I can goall the way through the routines, including what appears to be addingthe same item to the cart as before, only to find out that I am on acached page, and none of it really happened. This also causes problemswith a WebMerchant page that I am using. After someone makes a purchaseon my customer's site, I simply use a meta refresh tag to keep recyclingthe page until the approval is processed, and the WebMerchant approvedpage is written to disk. Then, I change the refresh interval to 0, andchange the redirect location to take the customer to that written page.Now, however, that page just keeps going in a circle, even aftertheWebMerchant page is written.Thanks,Dennis#############################################################This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to Dennis J. Bonsall, Jr.

DOWNLOAD WEBDNA NOW!

More on the template cache problem...

2000

Top Articles:

Related Readings: