Re: Session state is not available in this context
From: A.M (IHateSpam_at_sapm123.com)
Date: 03/30/04
- Previous message: Guillermo: "RE: Win2003 and NT AUTHORITY\NetworkService"
- In reply to: [MSFT]: "RE: Session state is not available in this context"
- Next in thread: Joe Kaplan \(MVP - ADSI\): "Re: Session state is not available in this context"
- Reply: Joe Kaplan \(MVP - ADSI\): "Re: Session state is not available in this context"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 30 Mar 2004 08:28:03 -0500
Thank you for reply.
Is the Cache's scope at application level or session level ? Does it keep
data for all session long? If it is so, generally why would I use Session
object if i have Cache object?
Thanks
Ali
"[MSFT]" <lukezhan@online.microsoft.com> wrote in message
news:zuH0$DjFEHA.3568@cpmsftngxa06.phx.gbl...
> Hi Ali,
>
> AuthenticateRequest event is raised right after a user has been
> authenticated but still has not been authorized meaning that aplication
has
> not decided on the areas that this user can have access to. And this
stage,
> application hasn't acquired the state also. So there is no session state
at
> this point. You can use the Cache object as Joe suggest.
>
> Regards,
>
> Luke
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
- Previous message: Guillermo: "RE: Win2003 and NT AUTHORITY\NetworkService"
- In reply to: [MSFT]: "RE: Session state is not available in this context"
- Next in thread: Joe Kaplan \(MVP - ADSI\): "Re: Session state is not available in this context"
- Reply: Joe Kaplan \(MVP - ADSI\): "Re: Session state is not available in this context"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|