A thought just came to me. Many people use CF for logging and the logging 'takes up' time on a page, slowing it down. Why bother? Most logging is just posting information to a DB and returns nothing to the page. Here's my solution to logging being a bottleneck: Asynchronous logging.
When you want to log a page, you just call an asynchronous gateway on CF 7 and pass it all the info you want to log. If it fails, it fails. If it succeeds then it has all the info it needs to go through. No real 'hit' to the page being called other than the calling of the gateway. The page does not wait for a result, it does not care if the logging table times out or fails, it just goes on. What do you think? Any flaws in my logic? Will an asynchronous gateway used for logging be a different form of bottleneck? Too much overhead (as its another page being run)? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:199023 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
