Code Comments

Programming Forum and web based access to our favorite programming groups.
For Programmers: Free Programming Magazines | New: Database administration forum
Registration is free! Edit your profileCalendarFind other membersFrequently Asked QuestionsSearch -> 
Post New Thread











Thread
Author

Session.abandon but NOT ASP.Net
I'm calling a webpage from an application..not a web application, not
a browser... but rather getting some timing and content verification,
so its a windows app that will eventually be transformed into a
service.

Using C# I'm doing a WebRequest.Create(site); then
WebRequest.GetResponse(); and then reading the response stream to the
end and do my processing followed by a Close() on the response stream.
All well and good, BUT we're leaving an open session which then skews
timing results on subsequent calls because its way faster the second
or more times until a timeout occurs along the way and suddenly it
jumps back to the initial time.

Basically I'm looking for a way to kill the session after I've called
my page so that when I come back I'll look like a new user and have
the timing of a new session creation.  Is this possible from my end or
is this strictly a function of the asp or aspx on the other (web
server) end?

Report this thread to moderator Post Follow-up to this message
Old Post
Tom
11-16-04 11:54 PM


Re: Session.abandon but NOT ASP.Net
Tom@TheEnderles.org (Tom) wrote in message news:<ac0692b.0411110725.65c841bb
@posting.google.com>...

> Basically I'm looking for a way to kill the session after I've called
> my page so that when I come back I'll look like a new user and have
> the timing of a new session creation.  Is this possible from my end or
> is this strictly a function of the asp or aspx on the other (web
> server) end?

The best you could do from the client would be to kill your cookie.
This would effectively end your session, but it sounds like that's not
what you're looking for.

Probably the best you can do would be to make a separate page or
webservice to kill your session explicitly.  So you'd call
YourTimingThing.aspx, followed by KillSession.aspx from your client
application on every iteration.

Good luck!

Jason
http://www.expatsoftware.com/

Report this thread to moderator Post Follow-up to this message
Old Post
Jason Kester
11-16-04 11:54 PM


Re: Session.abandon but NOT ASP.Net
Tom@TheEnderles.org (Tom) wrote in message news:<ac0692b.0411110725.65c841bb
@posting.google.com>...

> Basically I'm looking for a way to kill the session after I've called
> my page so that when I come back I'll look like a new user and have
> the timing of a new session creation.  Is this possible from my end or
> is this strictly a function of the asp or aspx on the other (web
> server) end?

The best you could do from the client would be to kill your cookie.
This would effectively end your session, but it sounds like that's not
what you're looking for.

Probably the best you can do would be to make a separate page or
webservice to kill your session explicitly.  So you'd call
YourTimingThing.aspx, followed by KillSession.aspx from your client
application on every iteration.

Good luck!

Jason
http://www.expatsoftware.com/

Report this thread to moderator Post Follow-up to this message
Old Post
Jason Kester
11-22-04 08:58 AM


Sponsored Links




Last Thread Next Thread Next
Search this forum -> 
Post New Thread

C# archive

Show a Printable Version Send to friend Email This Page to Someone! subscribe to this thread Receive updates to this thread
Computer Consultants
Programming Jobs
Visual Basic Controls
SQL Server Programming
Webservices
Java Security
Visual Studio
C# Programming
Visual J++
Software engineering
Open source Software
Perl Programming
PHP Programming
ASP Programming
ASP .NET Programming
Visual Basic Programming
Windows Scripting Host
Java Programming
Java Help
Java Beans
VBScript
Cobol
MAC Applications
Unix Programming
Forum Jump:
All times are GMT. The time now is 06:08 AM.

 
Free MCSE Braindumps | Real Estate Topics

Programming forum archive

Copyrights CodeComments.com 2004 - 2006

Powered by vBulletin Copyright 2000-2006 Jelsoft Enterprises Limited.