On 7/26/05, Adam Cameron <[EMAIL PROTECTED]> wrote: > I just think - on long processes - it might be more useful to see some > of the debugging stuff as it happens, rather than after it happens. > Given CF has the stuff "in there somewhere", I was wondering if it was > possible to liberate it.
Presumably, MM could add an additional debugging option like "output to a logfile" for each debug event category, which would write any debug events to a file on the server as they were triggered, thus allowing a dev to use 'tail -f' (or some equivalent) to view any updates to the file in real time. Unfortunately, I don't think such a thing exists today, and I think that you'd need access to the cfmx runtime src to build one yourself. -dante ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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/cfcdev@cfczone.org
