Quote:
|
Originally Posted by NichePay - StuartD
I'm not sure I get it quite right, but it seems to me that your server and database will do the same amount of work either which way, just at a different time in the page load. And if this is the case, then perhaps caching stats? Writing to a file? sessions and then session dumping after?
I dunno... just seems like having javascript do stuff when they close their browser will result in a LOT of lost data and won't save much if anything on serve load.
|
You're probably right for the amount of data loses but I want to test it ... Cause no it won't do the same amount of work for the server ... If I can use Javascript the way I want I will be able to connect to my database and update it only once instead of "X" numbers of time (depending of what my surfers do on my site).
Might represent a good saving (Processing power) if my site gets lot of traffic.