In that case, I'd say a collection or an array would be ideal - because you
can easily iterate through the elements..
"Abhilash.K.M" <abhilashkm@indiatimes.com> wrote in message
news:07c701c36b57$85255910$a101280a@phx.gbl...[color=blue]
> I will elaborate my requirments
>
> We are developing a mobile web application using ASP.NET
> in a web farm & not planning to use cookies as some
> device browser doesn't support the same.So we are doing
> the session management with the dot frame work provided
> session management using sql server with the values
> entered in WEB.CONFIG file.
> Now we need to set some 20 values to the session .so my
> question is whether we need to add individually as
> session values or store all the 20 values as key value
> pair(say collections).So which is better 1 0r 2?
>
> 1. There are 20 session variables and all of them[color=green][color=darkred]
> >> are being stored into session and accessed from session
> >> and individual session object. Example: Session["a"]
> >> = "XYZ", Session["b"]=100, Session["c"]="NAME", etc.
> >> where values are of primitive data type or immediate
> >> derivative of the primitive data types.
> >>
> >> 2. There are 20 session variable, a custom object[/color][/color]
> is[color=green][color=darkred]
> >> created out of them. The custom object is stored into[/color][/color]
> the[color=green][color=darkred]
> >> session. Example: NameValueCollection is an object[/color][/color]
> where[color=green][color=darkred]
> >> data will be stored as NameValueCollection["a"][/color][/color]
> = "XYZ",[color=green][color=darkred]
> >> NameValueCollection["b"]=100, NameValueCollection["c"]
> >> ="NAME". Finally while storing it in the session the
> >> NameValueCollection is used as Session["DATA"]=
> >> NameValueCollection.[/color][/color]
>
>[color=green]
> >-----Original Message-----
> >Some people would disagree, but for the past few years -[/color]
> I pretty much[color=green]
> >consider a SQL server an immediate part of my[/color]
> application. If you have a[color=green]
> >local, semi-robust SQL server - then making calls (like[/color]
> storing session[color=green]
> >information) is pretty negligable..
> >
> >So, I would say - you should have a SessionID - write[/color]
> that out as a cookie[color=green]
> >to the client.. then in a database, you have a SessionID[/color]
> that relates to[color=green]
> >whatever session data that you need...
> >
> >Same with traditional ASP - "Session" variables are[/color]
> really a bad idea. Even[color=green]
> >if you are not on a cluster/server farm now - at some[/color]
> point you will, and[color=green]
> >that is going to jam up your whole way of dealing with[/color]
> session data. The[color=green]
> >Session object stores things on the local server. So in[/color]
> a server farm[color=green]
> >scenario.. you go to the alias name, and are connected[/color]
> to server1, session[color=green]
> >variables are saved - ON server1. Then you click a link,[/color]
> go to the alias -[color=green]
> >and THIS time you go to server2. When it goes to process[/color]
> your request, it[color=green]
> >can't - because it's not the server where your session[/color]
> data exists... So,[color=green]
> >imho - it's just better to stay away from those and[/color]
> adopt a system that runs[color=green]
> >on everything, and even runs when you get into a[/color]
> scenario when you need[color=green]
> >highly-available servers...
> >
> >hth
> >
> >"Abhilash.k.m" <abhilashkm@indiatimes.com> wrote in[/color]
> message[color=green]
> >news:0d7c01c36b53$aef58750$a001280a@phx.gbl...[color=darkred]
> >> This is regarding the session management using Out of
> >> proc session management(SQL SERVER). Among the samples
> >> below which one is better to set the session?
> >>
> >>
> >>
> >> 1. There are 20 session variables and all of them
> >> are being stored into session and accessed from session
> >> and individual session object. Example: Session["a"]
> >> = "XYZ", Session["b"]=100, Session["c"]="NAME", etc.
> >> where values are of primitive data type or immediate
> >> derivative of the primitive data types.
> >>
> >> 2. There are 20 session variable, a custom object[/color][/color]
> is[color=green][color=darkred]
> >> created out of them. The custom object is stored into[/color][/color]
> the[color=green][color=darkred]
> >> session. Example: NameValueCollection is an object[/color][/color]
> where[color=green][color=darkred]
> >> data will be stored as NameValueCollection["a"][/color][/color]
> = "XYZ",[color=green][color=darkred]
> >> NameValueCollection["b"]=100, NameValueCollection["c"]
> >> ="NAME". Finally while storing it in the session the
> >> NameValueCollection is used as Session["DATA"]=
> >> NameValueCollection.
> >>
> >> 3)Is there any performance issue due to session
> >> management through SQL SERVER provided by DOTNET[/color][/color]
> framework[color=green][color=darkred]
> >>
> >>[/color]
> >
> >
> >.
> >[/color][/color]
