On 10/29/07, Leigh <[EMAIL PROTECTED]> wrote: > > > A couple of more questions! > > 1. My ldap.cfc currently has an attribute (qryUserDetails) that stores > a query record from an ldap lookup (which can then be read by other > objects). If I have the the two instances of the ldap.cfc instantiated > permanantly, then I cannot have this query as an attribute (as it > would be updating on every login request and require app scope > locking) - I guess then that I should instead then just be passing > qryUserDetails back out to the calling method in the securityManager?
I'm not saying it's impossible that you could want a stateful LDAP component, just that it doesn't seem like it is necessary in the context you've described. I'd have a a stateless LDAP component(s) that hits the LDAP server(s) and returns the results back to the SecurityManager. 2. If my securityManager is a singleton (which makes sense that it > is), what is basic method for passing messages out of it and back to > the calling listener? For example, if my listener function calls > securityManager.validateLogin(), I guess I could return a structure > (structResponse) which has keys structResponse.validated (true.false) > and structResponse.message (where in the listener this message could > be moved into the Event object for output in the view? I do something along that line. I actually prefer to have a generic Result object that the the Managers/Services can return to the Controller with methods like isSuccess(), hasErrors(), getErrorCollection(), etc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
