> I went ahead with the cookie method via javascript, which > fires off when > the user clicks the "Submit" button. Seems to be a good ballpark > estimate of how long the process took. It never needed to be > spot-on, > just an estimate. Works out just fine. Thanks for all the > great ideas!
Well, like Claude said, with this method you have to compare client side vs. server side. This is bad because of simple clock differences, time zones, etc. Unless you are using JS on the landing page to get the end time and do the math. That way both times come from the client, but you still have to get the data back to your server. ---------- This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:242596 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
