Re: It might be time for a refactor when...

Not all applications lend themselves to a web based interface. One IBM
i based company implemented SAP at the counters at all locations.
Transaction time went from several seconds to almost 2 minutes.
Contractors waiting for their parts for the day lost time waiting and
eventually found other suppliers. Sales went down, they had to build a
faster interface to fix it. Cost lots of lost sales and time to fix it.
They recovered but at what cost? The web based apps are not always the
solution.


Jim Oberholtzer
Agile Technology Architects

On Jul 23, 2024, at 3:46 PM, Raul Alberto Jager Weiler <

raul.jager@xxxxxxxxx> wrote:

You era right, it is necessary to plan for clean up.
And it takes practice to get used to the stateless environments, but once
you get used to it you will never miss the state full conexión.
The clean up is a small price compared with the advantages of the

stateless

conexión.

El mar, 23 de jul de 2024, 15:11, Daniel Gross <daniel@xxxxxxxx>

escribió:

Von meinem iPad gesendet

Am 23.07.2024 um 18:58 schrieb Raul Alberto Jager Weiler <

raul.jager@xxxxxxxxx>:

Also, the use of green screen or fat clients is a good reason to

refactor.

WEB user interfaces is much better.

Of course, web interfaces are the current "state-of-the-art" - but I

have

to say, that (at least IMHO) they lack one important feature: Stateful
Transaction Processing

All web interfaces are stateless by definition. They emulate a
statefulness by utilizing a bunch of technologies, like a shopping cart

or

a session token or something like that.

But in the end, if an session ends "abnormal" - there have to be

timeouts

and algorithms that detect inactive sessions to rollback database

actions -

where an aborted green screen session does all that without any

application

overhead.

So when in comes to transactions - maybe a stateful and transactional

user

interface is not the wrong choice.

Just my 2ct
Daniel
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.