Sharing ASP State

Resource Specification

Category:

ASP : Books

Title / Program Name:

Sharing ASP State

URL:

http://www.amazon.com/exec/obidos/ASIN/B00006LJ67/bigwebmasters-20

Screenshots URL:

http://www.bigwebmaster.com/screenshots/B00006LJ67.jpg

Released Date:

September 20, 2001

Cost:

$8.00

List Price:

$8.00

Pages:

8

Edition:

e-book (Acrobat Reader)

ISBN:

B00006LJ67

Publisher:

Wrox

Author:

David Gerding

Keywords:

creating companion sessions, killing companion sessions, asp.net redirects, asp.net links, asp.net cookies, asp.net caveats, asp.net security loophole, asp.net sessions variables, asp.net session management, asp.net application state, asp.net scope, asp.net virtual directory, asp.net article

Summary:

With ASP.NET

Description:

Developers with ASP based applications that use session and application state management (i.e. "session variables") are stuck if you want to gradually migrate existing state using applications to ASP.NET. Even though ASP.NET provides both session and application state management, they each run in their own scope. ASP and ASP.NET apges can cohabitate in the same virtual directory, but Sessions and the Application scope in ASP.NET's ASPx pages are disctinct from ASP pages in teh same virtual directory. However there is a way through this mess, and in this article David Gerding will show it to you. In the article Sharing ASP State with ASP.NET by David Gerding (published in ASP Today), the problem is throughly discussed and then moves on the the solution - "Companion Sessions". The article talks about initializing the companion sessions, the ASP Side of the Fence, Redirect/Links from ASP Pages to .NET, Cookies and Caveats, and security loophole.

Ratings Breakdown

Number of Votes:

0

Resource Rating:

0

Highest Rating:

N/A

Lowest Rating:

N/A

Rating	Vote %	# of Votes
10	0%	0
9	0%	0
8	0%	0
7	0%	0
6	0%	0
5	0%	0
4	0%	0
3	0%	0
2	0%	0
1	0%	0