To expand on what Max said: In application.cfm 1) if there is no structure, create a structure in the application scope named application.requests 2) Generate a UUID for this request 3) store request info which you want to track into application.requests[UUID] 4) Store the time of request
In onrequestend.cfm 1) delete the struct entry for UUID You will also need to perform cleanup of application.requests in case of erroring out. You may do this in two ways: 1) delete the struct entry for UUID in your error-handling page 2) arbitrarily decide that all requests greater than some preset length of time are invalid, and just clear out those entries. > You can also generate a unique ID (a UUID for > instance, or a random number) in the application.cfm > and log that to the DB with the request data. The > unique ID is then available throughout the request > for identifying that request "thread" and is > available in onRequestEnd.cfm to delete/close out > that log entry in the DB. > > -Max > > > ----------------------------- > Maxim Paperno, CTO > World Design Group, Inc. > [ CF Development and Hosting since 1996 ] > <http://www.WorldDesign.com/> ===== I-Lin Kuo Macromedia CF5 Advanced Developer Sun Certified Java 2 Programmer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
