> I'd suggest you create a basic error object with the methods you've > outlined above, then cache it in the session scope.
The thought of putting something like this into a session scope seems like it would use resources that it shouldn't necessarily be hitting. It makes me a little nervous to require the usage of a user's scoped object in order for the object to work. This would basically preclude the use of the component from any usage outside of the application, since some other application it might live under may not support sessions (such as a web service or something along those lines). Otherwise everything else sounded great :) Dan ---------------------------------------------------------- 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). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
