Actually, the best way is to create AuthenticationManager singleton
that handles all authentication business logic and notifies subscribed
views using events with types SIGN_IN and SIGN_OUT. Due to the fact
there could be some authentication views in application (e. g. form
and window), you should type them as IAuthenticationView and register
with AuthenticationManager. IAuthenticationView interface can provide
getters for username, password, isPersistent and showError() method.

On 8/9/06, Mike Anderson <[EMAIL PROTECTED]> wrote:
> Okay, sounds good to me!


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to