Jeff Watkins, el domingo 8 de enero a las 21:08 me escribiste: > Traditionally, the solution to this problem is to store information > about the visit in RAM (think the standard ASP or JSP session). But > that doesn't work too well if you have a multi-process or multi- > server environment, because those processes or servers must share > memory (not impossible, but it drives up the cost of clustering > significantly). > > A more robust solution is to store this information in a shared > database. It also provides for sessions (or visits) which can span > reboots of a server (which happens all the time under Windows).
Great, so why don't we use the session filter so anyone can use the model that better fits his needs (RAM/files/DB) and we don't have to discuss about confirmation of cookies? If DB sessions backend is broken, I don't think it would be impossible to fix. -- Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/ .------------------------------------------------------------------------, \ GPG: 5F5A8D05 // F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05 / '--------------------------------------------------------------------' "All mail clients suck. This one just sucks less." -me, circa 1995
