×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
You should be able to save it server side. You're right session
eventually expire/recycle/etc.
http://msdn.microsoft.com/en-us/library/ms178581.aspx
-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H.
Leverich
Sent: Monday, September 14, 2009 11:17 AM
To: .net use with the System i
Subject: Re: [SystemiDotNet] IIS server not sending user id
So you will have to save your _myDB2provider into a Session variable
and use it from there.
I would rather re-connect on each request. Also, can you even save a
connection in session? Perhaps is session is inproc since the connection
will stay active as the object isn't serialized inproc. But if you move
to a state server or sql or other persistence setup then the connection
would die anyway.
This is one of the reasons I require my devs to run w/session server and
not inproc. I've seen lots of stuff that works inproc and not out of
proc, but never seen the reverse. This way they can't do something that
won't work in production.
midrange.com
