Re: Interactive logic-style question

[Chris Holko <christopherholko@xxxxxxxxx>]

MVC is so overkill for most apps the only place more overkill is the number
of times its given as a response.

while the amount of time spent to evaluate a select structure or if when
else clause is small the developer should always minimize it when they have
knowledge of frequency. Getting into that habit early is one of the best
tips out there.

On Mon, Apr 20, 2015 at 8:27 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

> Bob,
>
> As far as style is concerned, my only objection would be the use of the #
> character as a variable prefix. But I understand that each shop has their
> own naming conventions, and I don't expect others to have the same as mine.
>
> As far as structure is concerned, it's well formed; much better than a lot
> of alternatives.
>
> Regarding performance, we're talking very few microseconds to evaluate a
> "when" condition. Contrast that with most web application environments
> which "route" browser requests to appropriate "servers", whether they be
> Java servlets, or scripts running under interpreted environments, you will
> find a comparatively HUGE amount of overhead in the latter.
>
> Your structure for dispatching requests based on #WrkMode could be viewed
> as the "controller", following a Model/View/Controller design pattern. Bind
> your controller to a *SRVPGM which implements procedures to handle screen
> I/O, then bind that *SRVPGM to another *SRVPGM which implements database
> I/O. Now you have an application that implements a very maintainable MVC
> design pattern.
>
> Nathan.
> --
> This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.