I've come from the old ASP camp where session variables were not used. When
i started using ASP.NET in 2001, I started using them again because it was
ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around that
session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
31  6998 
Session variables - bad.
All the session state schemes rely on a centralized model - that can never
be good for scaleability.
But if it means you will have to write tonnes of code for a website that has
5 concurrent users, then go ahead use 'em. (never overarchitect).
- Sahil Malik
You can reach me thru my blog at http://www.dotnetjunkies.com/weblog/sahilmalik
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because it was
ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around that
session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
We use it only if there is no other (easy) way.
Basicly its not done or you have to have a very good reason.
And if you dont clean them up when you're done with them....you'll get
punished ...;-)
Most variables can be covered by the viewstate and querystring to pass them
to an other screen.
But thats just our policy I guess....
"Harry Simpson" <hs*******@nosp amphgt.net> schreef in bericht
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because
it was ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around that
session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
I disagree with the two answers given so far, sessions in ASP were evil 'cuz
they were stored in the same memory space as the worker process. This is
true in ASP.Net as well when you have it set for InProc. It isn't true for
either StateServer or SQLServer. As far as scalability, SqlServer mode
scales very well and doesn't rely on a centralized model (no more so than
any other SQL Server database). What's even better is how easy it is to
switch modes - so long as you were careful to design all objects which are
to be stored in sessions as serializable (normally achieved simply by
specifying the ISerializableAt tribute() to the class) you simply change your
web.config and off you go.
Finally, ASP.Net 2.0's provider model will provide even more choice.
Karl
--
MY ASP.Net tutorials http://www.openmymind.net/
"Sahil Malik" <co************ *****@nospam.co m> wrote in message
news:O5******** ******@TK2MSFTN GP09.phx.gbl... Session variables - bad.
All the session state schemes rely on a centralized model - that can never
be good for scaleability.
But if it means you will have to write tonnes of code for a website that
has 5 concurrent users, then go ahead use 'em. (never overarchitect).
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because it
was ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around that
session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
My view is that session variables can be good when you need to store object
information or large amounts of data per session without having to make
repeat database calls every time.
This still shouldn't be an excuse for good design. You should also ensure
you dispose of your session variables properly so they aren't hanging around
taking up memory.
In most cases though I opt for using querystring parameters, cookies, hidden
fields or ViewState to manage session information.
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because
it was ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around that
session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
Allright, I disagree .. Let me explain why --- As far as scalability, SqlServer mode scales very well and doesn't rely
on a centralized model (no more so than any other SQL Server database).
SqlServer scalability is acheived using failover and clustering. Not using
Network Load Balancing and Web Farms (redundancy). Web farm machines are by
far much cheaper than Sql server clustering architecture. What's more, by
using Session variables and not specifying state server, you loose any
prayer of ever being able to use a webfarm well enough. Not to mention, you
have one point of failure, and hardware limitations on that one poor box
acting as the state machine. By using a state server you donot lock yourself
up into an app that will never scale - but you make it pretty damn expensive
to scale in future - which is the whole point, you want to acheive
scalability cheaply by adding/removing machines at runtime without bringing
the entire site down. (therefore www24.microsoft .com).
What's even better is how easy it is to switch modes - so long as you
were careful to design all objects which are to be stored in sessions as
serializable (normally achieved simply by specifying the
ISerializableAt tribute() to the class) you simply change your web.config and
off you go.
Objects in session are even worse. If you have a memory leak, you just
fixated that memory leak in a process that won't die (IIS). Not to mention
there is nothing like ISerializableAt tribute, but there is a
SerializableAtt ribute and an ISerializable interface. SerializableAtt ribute
works .. well most of the times; but first of all it's behavior is limited,
(it's not that smart), and it has troubles with protected members and
delegates.ISeri alizable on the other hand depends on the programmer's
efficacy - which I try and not rely on in a website that is highload -
typically multi megabyte source code - you cannot practically enforce good
programming all over.
Finally, ASP.Net 2.0's provider model will provide even more choice.
Makes no difference to the above facts.
The rule is - Try very hard to avoid session - but don't put yourself in a
hospital trying to avoid it.
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
"Karl Seguin" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME net>
wrote in message news:%2******** ********@TK2MSF TNGP14.phx.gbl. .. I disagree with the two answers given so far, sessions in ASP were evil
'cuz they were stored in the same memory space as the worker process. This is
true in ASP.Net as well when you have it set for InProc. It isn't true
for either StateServer or SQLServer. As far as scalability, SqlServer mode
scales very well and doesn't rely on a centralized model (no more so than
any other SQL Server database). What's even better is how easy it is to
switch modes - so long as you were careful to design all objects which are
to be stored in sessions as serializable (normally achieved simply by
specifying the ISerializableAt tribute() to the class) you simply change
your web.config and off you go.
Finally, ASP.Net 2.0's provider model will provide even more choice.
Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/
"Sahil Malik" <co************ *****@nospam.co m> wrote in message
news:O5******** ******@TK2MSFTN GP09.phx.gbl... Session variables - bad.
All the session state schemes rely on a centralized model - that can
never be good for scaleability.
But if it means you will have to write tonnes of code for a website that
has 5 concurrent users, then go ahead use 'em. (never overarchitect).
- Sahil Malik
You can reach me thru my blog at
http://www.dotnetjunkies.com/weblog/sahilmalik
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because it
was ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around
that session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
In programs past, I've never had more than about 50 concurrent users and
sessionstate has never been a problem (InProc et all).
How would one pass a dataset from one screen to the next if not with Session
State? Are you using global variables?
TIA
Harry
"Janaka" <ja*****@hotmai l.com> wrote in message
news:Oi******** ******@TK2MSFTN GP09.phx.gbl... My view is that session variables can be good when you need to store
object information or large amounts of data per session without having to
make repeat database calls every time.
This still shouldn't be an excuse for good design. You should also
ensure you dispose of your session variables properly so they aren't
hanging around taking up memory.
In most cases though I opt for using querystring parameters, cookies,
hidden fields or ViewState to manage session information.
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because
it was ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around that
session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
You can only get a "Contracter 's answer" for this. "It Depends".
If you are coming from the classic ASP background, you tend to shy away from
Session objects since they were wrought with issues in COM threading/server
affinity et al. With ASP.NET, most of these issues have a solution.
You can use Session for almost anything. Just be careful to make sure that
any objects you mght stuff in there are [serializable] if you ever want to
use StateSErver or SqlServer.
With 2.0, you get more choices for session management.
All in all, I dont see any reason to go out of your way to avoid Sessions.
--
Girish Bharadwaj http://msmvps.com/gbvb
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because it was
ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around that
session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
Thanks Sahil and Girish,
The web apps are just that apps used by a limited number of concurrent
users. It's not an E-bay or Amazon deal.
dataset and other builtin datatypes are serializable from the getgo right.
I just need to declare homegrown objects as such?
Appreciate your time and effort responding to this thread. Bottom line is
use minimally.
One other item, I've never cleaned up after my sessions because by
definition, the variables are destroyed when the session ends anyhoo....is
this not correct...? I haven't been bit yet by not cleaning up...
Harry
"Girish Bharadwaj" <gi*****@mvps.o rg> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. .. You can only get a "Contracter 's answer" for this. "It Depends".
If you are coming from the classic ASP background, you tend to shy away
from
Session objects since they were wrought with issues in COM
threading/server
affinity et al. With ASP.NET, most of these issues have a solution.
You can use Session for almost anything. Just be careful to make sure that
any objects you mght stuff in there are [serializable] if you ever want to
use StateSErver or SqlServer.
With 2.0, you get more choices for session management.
All in all, I dont see any reason to go out of your way to avoid Sessions.
--
Girish Bharadwaj
http://msmvps.com/gbvb
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because it
was
ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around that
session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
Harry,
Datasets are serializable, but their serialization format is XML (cannot
override; atleast not easily) which is ultra bloated.
Not all objects that come with .NET are serializable by default.
Your best bet is to implement simplistic structures to represent the data
you need to store in session - but again, try and avoid using session
variables.
- Sahil Malik
You can reach me thru my blog at http://www.dotnetjunkies.com/weblog/sahilmalik
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:eb******** ******@TK2MSFTN GP10.phx.gbl... Thanks Sahil and Girish,
The web apps are just that apps used by a limited number of concurrent
users. It's not an E-bay or Amazon deal.
dataset and other builtin datatypes are serializable from the getgo right.
I just need to declare homegrown objects as such?
Appreciate your time and effort responding to this thread. Bottom line is
use minimally.
One other item, I've never cleaned up after my sessions because by
definition, the variables are destroyed when the session ends anyhoo....is
this not correct...? I haven't been bit yet by not cleaning up...
Harry
"Girish Bharadwaj" <gi*****@mvps.o rg> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. .. You can only get a "Contracter 's answer" for this. "It Depends".
If you are coming from the classic ASP background, you tend to shy away
from
Session objects since they were wrought with issues in COM
threading/server
affinity et al. With ASP.NET, most of these issues have a solution.
You can use Session for almost anything. Just be careful to make sure
that any objects you mght stuff in there are [serializable] if you ever want
to use StateSErver or SqlServer.
With 2.0, you get more choices for session management.
All in all, I dont see any reason to go out of your way to avoid
Sessions.
--
Girish Bharadwaj
http://msmvps.com/gbvb
"Harry Simpson" <hs*******@nosp amphgt.net> wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. . I've come from the old ASP camp where session variables were not used.
When i started using ASP.NET in 2001, I started using them again because it
was
ok from what I'd read.
I've been merrily using Session variables for three years now and i'm
entering a project with my new boss who has never quite come around
that session variables are ok.
What's the concensus here. How can i convince him that they are ok in
ASP.NET. OR
Are there those out there that still think they aren't good to use?
TIA
Harry Simpson
MCSD
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Lina Manjarres |
last post by:
Hello,
I have a session variable in a login page. Then I go to a form page where I
uses the ProfileID and the UserID. Then I go to a result page where I would
like to use the UserID as a filter, but I can't get the value is stored in it.
How can I do that?
Thanks a lot!
|
by: Phillip N Rounds |
last post by:
I'm writing a user control which has two states: Active & InActive. I
additionally am required that there to be only one active control per page,
and all logic has to be contained within the control.
In its inactive state, only a single button appears. If the user clicks on
this button, the control becomes active( the rest of the control's
functionality becomes visible), and all other instances of this user control
on the page should...
|
by: Erik |
last post by:
I have an application that uses sessions variables a lot but one I publish
the application on the prod server these variables are lost. The application
is written i c# 2.0 and I've set the statServer timeout to 20 min in the the
web.config file. Any ideas why the variables are lost?
|
by: Michaelk |
last post by:
Can somebody tell me how many Session variables would be considered
exessive, and when they start really affect the server speed.
For example on 20-30 asp pages I need to use about 200-300 session variables
and 5 arrays by 1000 elements 50 characters long each.
Let say having 300 users using those pages at the same time.
Server is not the fastest one, just CPU 2.40GHz.
So question is as a user am I going to feel a difference in speed...
|
by: ChrisAtWokingham |
last post by:
I have been struggling with unexpected error messages on an ASP.NET system, using SQL and C#. The application draws organisation charts, based on data stored in the SQL database. Some of the chart editing processes place a very heavy load on the server as the effects of the edit ripple through the organisation structure, requiring potentially large numbers of rows in one of the tables to be updated. (I have done it this way to make the more...
| | |
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
| | |
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
|
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |
