×
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.
FWIW, My suggestion:
If you need sessions to persist, store the info in the SQL Server or
iSeries database.
The I/O hit is probably pretty-negligible unless you're storing large
amounts of data for a session.
Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 2
date: Wed, 6 Jan 2010 14:08:28 -0500
from: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
subject: Re: [SystemiDotNet] Web Service Session State
What volume are we talking about here? Why not just store the session db
on the iSeries if you don't already have a SQLServer infrastructure.
Unless we're talking about huge volumes here I would use the DB. I think
you're avoiding it for no good reason.
-Walden
midrange.com
