+1 Nathan...the thing that has made a "pure" i solution so viable is
that the web frontend of most apps is HTML5/CSS/JS because it is the
best overall solution that meets the variety of devices that will need
to display the web page. A well designed, responsive web app will
basically be HTML5/CSS/JS all of which is easily served by Apache on i.
The business logic that manages the data should naturally reside on i
(why have two tiers of business logic on two platforms?). So that is
where I end up scratching my head on ASP/i hybrid apps. What does ASP
bring to the party that can't be efficiently handled on i?
I work in a non-IBM i shop but the heavy lifting that ASP does is more
closely aligned with the MSSQL DB than anything else. Otherwise I could
move the Java/PHP code we have to i. ASP has a place in a shop where MS
has been the "legacy" app development provider but I have always
struggled to understand why in an IBM i centric shop other web
technologies displace what is already available on i.
GIAC Secure Software Programmer-Java
On 12/27/2014 12:02 PM, Nathan Andelin wrote:
It is of course a viable alternative to distribute development and
application workloads across both Microsoft and IBM i platforms but I also
recommend against it. You under-utilize your IBM i environment. It increase
the complexity and cost of your systems. Microsoft provides a platform for
viruses and other malware. It compromises security. Performance and
I promote IBM i on Power. It's sad to see application workloads move to
This mailing list archive is Copyright 1997-2020 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