> Don't blame Google for the errors of webdevelopers. The HTTP RFC > specifically says that GET request should not have lasting > side-effects: > > <quote> > In particular, the convention has been established that the > GET and > HEAD methods SHOULD NOT have the significance of taking an action > other than retrieval. These methods ought to be considered > "safe". > </quote> RFC 2616 > > Now if you'll excuse me, I have some applications to fix properly > instead of implementing some lame user agent detection workaround.
I'm still concerned about the effects of precaching, even if the requests don't do anything other than retrieval. Do you really want HTTP clients prefetching 10 dynamically-generated pages for every one they actually use? Especially if, for whatever reason, I can't cache them for reuse by other HTTP clients? Lame user agent detection, here I come! And while everything you say about the RFC is true, that doesn't absolve Google of all responsibility, just as I wouldn't be free to run over jaywalkers with my car. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:205960 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
