Re: How to keep persistant data between web apps

if you have a small amount of data, perhaps just store it (as one field
maching a DS on the AS400) into the html pages.
you'll be able to read them via the gethtmlvar (use a hidden field like
authinfos ...)

Hope this help

----- Original Message -----
From: "Scott Swaim" <scott@xxxxxxxxxxxxxxxx>
To: <MIDRANGE-L@xxxxxxxxxxxx>
Sent: Friday, February 18, 2005 4:05 PM
Subject: How to keep persistant data between web apps


> I am just now starting to program for the web.  I am running V5R1 (with
all
> current ptf's)  I am working through the easy400 deliverables and
modifying
> them to meet my needs.  I am trying to create a web application framework
> that would allow our Distributors to log into the website and then have
> access to there account information.
>
> The problem that I am facing now is try to keep data persistent between
> applications.  I know that I can create a session HANDLE that will allow
for
> persistent for one app.  I would like for the user to log in using my own
> auth method and then keep the information (i.e. customer number, agent
code,
> etc) to be used for other apps on the site.
>
> My first thought was to generate a session id that would then be written
to
> a file along with the additional info that I want to keep and then have a
> procedure that would retrieve the info based on the session id as the key.
>
> I am new to this area for web programming.  I would like to stay with RPG
as
> my language as that is what I am most familiar.  I am familiar with PHP
but
> I do not have the PASE environment installed on my machine to run PHP with
> my Apache server.
>
>
> Thank for any input.
>
>
> Scott Swaim
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>