Re: Net.Data and session management

Maybe I've used persistence wrong. More today than ever if anything causes
that session to submit the same url again it bombs out kicking the user out
and destroying the session causing the user to return to the beginning of
the process and start over. Double clicking a button, clicking again if
there is a delay, refreshing the page, everything craps it out and our user
base screams to high heaven of the issue. Is there a way to use persistence
and not have it bomb out with a double call?

***
Regards,
Joe W Holt
Sr Programmer/Developer
Jack Onofrio Dog Shows, LLC
405.427.8181



From: Nathan Andelin <nandelin@xxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
<web400@xxxxxxxxxxxx>
Date: 10/24/2014 01:21 PM
Subject: Re: [WEB400] Net.Data and session management
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>



Regarding the future of Net.Data, it appears very likely that the actual
program object (DB2WW.PGM) will continue be included in the distribution
for as long as IBM i is around, along with A LOT of other legacy *PGM and
*SRVPGM objects. But if your idea of "support" means continuing to extend
and enhance it, then I'm doubtful about that.

I'm not sure what you mean by "persistence" being frowned upon today. I
only find that in erudite circles. I would suggest that the number of
applications that use "persistent" database connections has grown steadily
irregardless of the naysayers. Otherwise the Internet would be rift with
functional deficits.

No, "persistence" maintained within processes (Jobs under IBM i) is very
much alive and well - and growing. Session data keyed by a value stored in
a cookie is also a good option. In my opinion, session data is best stored
in a database table which is cleared periodically.

Nathan.





On Fri, Oct 24, 2014 at 9:44 AM, Joe W Holt <joe.holt@xxxxxxxxxxx> wrote:

I've noticed an uptick of Net.Data users posting so I wanted to push out

a

question. Back when I adopted Net.Data (when it first came out) I

developed

with it as mainly an interface to maintain session management using
persistence and calling rpg programs. Well with the passage of time
persistence is frowned upon even more so today. It is way too easy to
create an error forcing the persistence to bomb out and eject the user
data. I'm quickly writing the replacement application and am being

pushed

by relevance of technology to use other tools such as php. Not a big
proponent of using php on my box. I prefer CGIDEV2 and such tools that

are

relatively unknown outside of the 400 circles so that they aren't readily
high profile attack options. As I examine my apache logs I see countless
times the efforts being made in the public to take advantage of known
attacks these other platforms have fallen prey.

Anyone else adopt some session management styles with Net.Data that

would

be nice to implement? I've started using CGIDEV2 and userspaces with
cookies but it isn't a very clean approach due to my own haste and am
rethinking my options. I'm either going to have to adopt another tool

like

php, clean up the CGIDEV2 process, or use Net.Data with??? Any thoughts
would be great. I'm not with great confidence that Net.Data will survive
as an available product as technology continues to change. I was very
surprised (and relieved) to have it on 7.1.



***
Regards,
Joe W Holt
Sr Programmer/Developer
Jack Onofrio Dog Shows, LLC
405.427.8181
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.