× 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.



I assume you are using a persistent connection, so i5_pconnect()?

Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi



Pete Helgren <pete@xxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
03/03/2011 01:56 PM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] persistent sign on for Zend Server






The technique I use is to use the user id and password to connect and
then make the connection object part of the session variable and use
that connection object when I need it.

Pete Helgren
Value Added Software, Inc
www.asaap.com
www.opensource4i.com


On 3/3/2011 12:18 PM, Larry Kleinman wrote:
Using Zend Server, I would like to present a sign-on screen where the
user
enters a user ID and password to be used as the parms of the i5_connect
function. This is not hard, but I want to present that screen only
once,
and use that info as the user moves from screen to screen, all of which
will require a 15_connection. I know that I can store the user and
password entered as $_SESSION variables, but I don;t like the idea of
the
password being written to some place on the PC hard drive. (That's how
$_SESSION works, right?). Any suggestions on how to deal with this.

Larry Kleinman
Kleinman Associates, Inc.
212-949-6469
203-255-4100

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.