Point well taken, thanks.

Then is there some type of publication that will guide you through those
options?
It always seems that third party books do that. But I have even found some
of them light with examples and explanations.

I am the first to admit I am not the sharpest tool in the shed. I am
fortunate that the company I work for has a computer programmer as
President. So he knows what it takes to do stuff. But I can really feel for
those who work for companies who have bosses who want results and want them
quick. And do not understand that it does days of research and trail and
error to get something simple to work at times.

After DDS, HTML and Java Script are tons of fun too. :)

And to Mikes response, yes thank God for this forum. I always try to
research before asking a question, it is a good way to learn more, but it
has given me answers to questions that I could not seem to find anywhere
else.

Ok, I will go find some cheese for my whine now....

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of BMay@xxxxxxxxx
Sent: Monday, November 09, 2009 10:16 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] PHP - authenticate and authorize using AS400 profile


Tom,

I think the main reason is that there are MANY different ways you could be
doing it. You could be prompting for user and password via Apache or your
own form. If it is your own form, once you have the signon and password,
you could be storing them as session variables, in an encrypted temp file
in the IFS, or any number of other scenarios. The example in the manual
is really just there to explain the i5_connect function. How you use it
is up to you.

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

Young i Professionals
http://www.youngiprofessionals.com



"Tom Deskevich" <thomas.l.deskevich@xxxxxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
11/09/2009 08:44 AM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


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

Subject
Re: [WEB400] PHP - authenticate and authorize using AS400 profile






Mike,

How about the i5_connect that is in mentioned in this thread?

Here is the example from the user guide:

$conn = i5_connect("1.2.3.4", "MYUSER", "MYPWD");
if (!$conn) {
die(i5_errormsg());
}

Why would the example have a hard-coded user name and password? Who would
do
that?
I am not picking on ZEND, this seems to be the norm. Every example is a
'hello world' example. Yet taking that to a practical step is where the
blood sweat and tears
come
in.

So where do I go from there to find out how to have the user key in their
user id and password? Mr. Google and forums like this, I guess. But
sometimes when you go to Mr. Google, you find that the examples out there
are not correct.

Ok, I am done ranting. Thanks for reading this.

Tom Deskevich


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Mike Pavlak
Sent: Monday, November 09, 2009 8:50 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] PHP - authenticate and authorize using AS400 profile


Tom,

Have you tried the Zend Core for i5/OS User Guide? It is located here and
there are many examples:
http://www.zend.com/topics/Zend-Core-User-Guide-i5OS-V261.pdf

Whether you consider them "good" or not is another discussion :-)

Also, which i5 functions do you have questions about? I have sample code
on
many of them and can provide if desired.

Regards,

Mike

mike.p@xxxxxxxx Cell: (408)679-1011 Office: (815)722-3454






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.