Re: Session Variables - why aren't novice developers warned?
- From: "Mark Rae" <mark@xxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Oct 2006 15:41:34 +0100
"BillE" <belgie@xxxxxxxxxxx> wrote in message
news:et7L5Es8GHA.2120@xxxxxxxxxxxxxxxxxxxxxxx
I expect there may be countless ASP applications deployed which are
silently adding orders to the wrong customer and the like because the
developer did not stumble across this issue.
I feel that, if that were indeed the case, then it would be down to woefully
inadequate (more like non-existent!) testing...
You can research session state very thoroughly without finding any
reference to this damaging problem.
http://www.google.co.uk/search?sourceid=navclient&ie=UTF-8&rls=GGLG,GGLG:2006-28,GGLG:en&q=IsNewSession
http://www.google.co.uk/search?sourceid=navclient&ie=UTF-8&rls=GGLG,GGLG:2006-28,GGLG:en&q=IsNewSession+%22new+window%22
.
- Follow-Ups:
- References:
- Session Variables - why aren't novice developers warned?
- From: BillE
- Re: Session Variables - why aren't novice developers warned?
- From: Mark Fitzpatrick
- Re: Session Variables - why aren't novice developers warned?
- From: BillE
- Re: Session Variables - why aren't novice developers warned?
- From: Marina Levit [MVP]
- Re: Session Variables - why aren't novice developers warned?
- From: BillE
- Session Variables - why aren't novice developers warned?
- Prev by Date: Re: How to get the remote port number in asp.net
- Next by Date: Re: Session Variables - why aren't novice developers warned?
- Previous by thread: Re: Session Variables - why aren't novice developers warned?
- Next by thread: Re: Session Variables - why aren't novice developers warned?
- Index(es):
Relevant Pages
|
Loading