On 7/26/05, Adam Cameron <[EMAIL PROTECTED]> wrote: > Sorry mate, I think we're talking at cross-purposes. > > I'm not interested in error-trapping, and adding my own logging stuff to > my templates, or anything like that. > > You know if you switch CF debugging on, you can get things like: > - the SQL that was executed; > - which templates were executed; > - how long they took to run; > all at the bottom of the HTML output for whatever request you've just > made? > > Well... I'm theorising that that information isn't all acquired *right > at the end of the request* (ie: where the debug template outputs it), > I'm theorising CF captures it *as it happens*. What I'd like to do is > to have access to it *as it happens* (ie: as the debugging service > gathers the info), so I can "listen" to it *as it happens*.
Well, my initial reaction is to ask you "what" exactly you're trying to do, or "why" you're trying to do it, but I think I know what you want. You want access to whatever internal structures the cfmx runtime uses to track the various data points needed for the debugging output. Is that right? If yes, then I think your options are limited. At best, you might be able to increase the logging level for the cfmx runtime, but I don't think that gets you what you want. -dante ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
