[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.aspnet.caching

Question on Stateless Architecture

SF

10/27/2006 7:18:00 AM

I have to design a website where the client wants it to be completly
stateless. By stateless I assume he means that he does not want to maintain
any state on the server side. Could anybody provide me any reference
materials as to how should I proceed. When a user logs in I need to pass on
username, userKey... to all the pages in the website. Thanks in advance..

Regards,
5 Answers

Mark Fitzpatrick

10/30/2006 1:02:00 AM

0

It could just be that the client doesn't want to use a session variable. The
funny thing is, the web is stateless anyways so maybe the client is getting
confused or means something slightly different. You could use the Membership
provider built right into ASP.Net with FormsAuthentication to take care of
the maintaining logged in user state against a db. It does the heavy work
and enables you to get the username as well as the users'd id through the
provideruserkey property.

I typically avoid a lot of state across pages. You can use viewstate within
a page if you need to to maintain the state within a page if absolutely
necessary. Perhaps the client is concerned about performance hits for using
sessionstate variables or possible issues with using sessionstate in a
webfarm or webgarden.


--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006


"SF" <SF@discussions.microsoft.com> wrote in message
news:710F2FF3-62E3-4A9B-8902-6243F32DC76A@microsoft.com...
>I have to design a website where the client wants it to be completly
> stateless. By stateless I assume he means that he does not want to
> maintain
> any state on the server side. Could anybody provide me any reference
> materials as to how should I proceed. When a user logs in I need to pass
> on
> username, userKey... to all the pages in the website. Thanks in advance..
>
> Regards,
>


SF

10/30/2006 6:36:00 AM

0

Thanks for the reply Mark. Yes the client does not want to use session
variables. I have to pass first name, Last Name, Dealer Number, UserKey etc
across the pages.
Can I store the above information in the membership provider. I was planning
to pass them using hidden variables, Query strings etc. Please suggest

Regards,SF

"Mark Fitzpatrick" wrote:

> It could just be that the client doesn't want to use a session variable. The
> funny thing is, the web is stateless anyways so maybe the client is getting
> confused or means something slightly different. You could use the Membership
> provider built right into ASP.Net with FormsAuthentication to take care of
> the maintaining logged in user state against a db. It does the heavy work
> and enables you to get the username as well as the users'd id through the
> provideruserkey property.
>
> I typically avoid a lot of state across pages. You can use viewstate within
> a page if you need to to maintain the state within a page if absolutely
> necessary. Perhaps the client is concerned about performance hits for using
> sessionstate variables or possible issues with using sessionstate in a
> webfarm or webgarden.
>
>
> --
> Hope this helps,
> Mark Fitzpatrick
> Former Microsoft FrontPage MVP 199?-2006
>
>
> "SF" <SF@discussions.microsoft.com> wrote in message
> news:710F2FF3-62E3-4A9B-8902-6243F32DC76A@microsoft.com...
> >I have to design a website where the client wants it to be completly
> > stateless. By stateless I assume he means that he does not want to
> > maintain
> > any state on the server side. Could anybody provide me any reference
> > materials as to how should I proceed. When a user logs in I need to pass
> > on
> > username, userKey... to all the pages in the website. Thanks in advance..
> >
> > Regards,
> >
>
>
>

SF

10/30/2006 8:07:00 AM

0

The other reason we don't want to session variables is because of the
performance reasons. Will Profile object have the same sort of performance
hit as compared to the session object?


"SF" wrote:

> Thanks for the reply Mark. Yes the client does not want to use session
> variables. I have to pass first name, Last Name, Dealer Number, UserKey etc
> across the pages.
> Can I store the above information in the membership provider. I was planning
> to pass them using hidden variables, Query strings etc. Please suggest
>
> Regards,SF
>
> "Mark Fitzpatrick" wrote:
>
> > It could just be that the client doesn't want to use a session variable. The
> > funny thing is, the web is stateless anyways so maybe the client is getting
> > confused or means something slightly different. You could use the Membership
> > provider built right into ASP.Net with FormsAuthentication to take care of
> > the maintaining logged in user state against a db. It does the heavy work
> > and enables you to get the username as well as the users'd id through the
> > provideruserkey property.
> >
> > I typically avoid a lot of state across pages. You can use viewstate within
> > a page if you need to to maintain the state within a page if absolutely
> > necessary. Perhaps the client is concerned about performance hits for using
> > sessionstate variables or possible issues with using sessionstate in a
> > webfarm or webgarden.
> >
> >
> > --
> > Hope this helps,
> > Mark Fitzpatrick
> > Former Microsoft FrontPage MVP 199?-2006
> >
> >
> > "SF" <SF@discussions.microsoft.com> wrote in message
> > news:710F2FF3-62E3-4A9B-8902-6243F32DC76A@microsoft.com...
> > >I have to design a website where the client wants it to be completly
> > > stateless. By stateless I assume he means that he does not want to
> > > maintain
> > > any state on the server side. Could anybody provide me any reference
> > > materials as to how should I proceed. When a user logs in I need to pass
> > > on
> > > username, userKey... to all the pages in the website. Thanks in advance..
> > >
> > > Regards,
> > >
> >
> >
> >

Mark Fitzpatrick

11/12/2006 3:04:00 PM

0

From what I've seen of the profile and membership providers they do a great
job performance-wise. It's also possible to combine them with some caching
techniques to get better performance. For example, if you have a control
that shows their name on each page if they're logged in, you could create a
caching mechanism to store the profile information based on their ID.

--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006


"SF" <SF@discussions.microsoft.com> wrote in message
news:2EBDB353-68E4-44FC-988D-3CE2167EF57A@microsoft.com...
> The other reason we don't want to session variables is because of the
> performance reasons. Will Profile object have the same sort of performance
> hit as compared to the session object?
>
>
> "SF" wrote:
>
>> Thanks for the reply Mark. Yes the client does not want to use session
>> variables. I have to pass first name, Last Name, Dealer Number, UserKey
>> etc
>> across the pages.
>> Can I store the above information in the membership provider. I was
>> planning
>> to pass them using hidden variables, Query strings etc. Please suggest
>>
>> Regards,SF
>>
>> "Mark Fitzpatrick" wrote:
>>
>> > It could just be that the client doesn't want to use a session
>> > variable. The
>> > funny thing is, the web is stateless anyways so maybe the client is
>> > getting
>> > confused or means something slightly different. You could use the
>> > Membership
>> > provider built right into ASP.Net with FormsAuthentication to take care
>> > of
>> > the maintaining logged in user state against a db. It does the heavy
>> > work
>> > and enables you to get the username as well as the users'd id through
>> > the
>> > provideruserkey property.
>> >
>> > I typically avoid a lot of state across pages. You can use viewstate
>> > within
>> > a page if you need to to maintain the state within a page if absolutely
>> > necessary. Perhaps the client is concerned about performance hits for
>> > using
>> > sessionstate variables or possible issues with using sessionstate in a
>> > webfarm or webgarden.
>> >
>> >
>> > --
>> > Hope this helps,
>> > Mark Fitzpatrick
>> > Former Microsoft FrontPage MVP 199?-2006
>> >
>> >
>> > "SF" <SF@discussions.microsoft.com> wrote in message
>> > news:710F2FF3-62E3-4A9B-8902-6243F32DC76A@microsoft.com...
>> > >I have to design a website where the client wants it to be completly
>> > > stateless. By stateless I assume he means that he does not want to
>> > > maintain
>> > > any state on the server side. Could anybody provide me any reference
>> > > materials as to how should I proceed. When a user logs in I need to
>> > > pass
>> > > on
>> > > username, userKey... to all the pages in the website. Thanks in
>> > > advance..
>> > >
>> > > Regards,
>> > >
>> >
>> >
>> >


SF

11/23/2006 9:59:00 AM

0

Thanks for the reply. Client does not want to use any state whatsoever on the
server side. So I ws planning to use client side state management.

Thanks,


"Mark Fitzpatrick" wrote:

> From what I've seen of the profile and membership providers they do a great
> job performance-wise. It's also possible to combine them with some caching
> techniques to get better performance. For example, if you have a control
> that shows their name on each page if they're logged in, you could create a
> caching mechanism to store the profile information based on their ID.
>
> --
> Hope this helps,
> Mark Fitzpatrick
> Former Microsoft FrontPage MVP 199?-2006
>
>
> "SF" <SF@discussions.microsoft.com> wrote in message
> news:2EBDB353-68E4-44FC-988D-3CE2167EF57A@microsoft.com...
> > The other reason we don't want to session variables is because of the
> > performance reasons. Will Profile object have the same sort of performance
> > hit as compared to the session object?
> >
> >
> > "SF" wrote:
> >
> >> Thanks for the reply Mark. Yes the client does not want to use session
> >> variables. I have to pass first name, Last Name, Dealer Number, UserKey
> >> etc
> >> across the pages.
> >> Can I store the above information in the membership provider. I was
> >> planning
> >> to pass them using hidden variables, Query strings etc. Please suggest
> >>
> >> Regards,SF
> >>
> >> "Mark Fitzpatrick" wrote:
> >>
> >> > It could just be that the client doesn't want to use a session
> >> > variable. The
> >> > funny thing is, the web is stateless anyways so maybe the client is
> >> > getting
> >> > confused or means something slightly different. You could use the
> >> > Membership
> >> > provider built right into ASP.Net with FormsAuthentication to take care
> >> > of
> >> > the maintaining logged in user state against a db. It does the heavy
> >> > work
> >> > and enables you to get the username as well as the users'd id through
> >> > the
> >> > provideruserkey property.
> >> >
> >> > I typically avoid a lot of state across pages. You can use viewstate
> >> > within
> >> > a page if you need to to maintain the state within a page if absolutely
> >> > necessary. Perhaps the client is concerned about performance hits for
> >> > using
> >> > sessionstate variables or possible issues with using sessionstate in a
> >> > webfarm or webgarden.
> >> >
> >> >
> >> > --
> >> > Hope this helps,
> >> > Mark Fitzpatrick
> >> > Former Microsoft FrontPage MVP 199?-2006
> >> >
> >> >
> >> > "SF" <SF@discussions.microsoft.com> wrote in message
> >> > news:710F2FF3-62E3-4A9B-8902-6243F32DC76A@microsoft.com...
> >> > >I have to design a website where the client wants it to be completly
> >> > > stateless. By stateless I assume he means that he does not want to
> >> > > maintain
> >> > > any state on the server side. Could anybody provide me any reference
> >> > > materials as to how should I proceed. When a user logs in I need to
> >> > > pass
> >> > > on
> >> > > username, userKey... to all the pages in the website. Thanks in
> >> > > advance..
> >> > >
> >> > > Regards,
> >> > >
> >> >
> >> >
> >> >
>
>
>