Dave O. wrote:
As to your application... it sounds somewhat like I want, probably
more for my needs near term.
By "your application", do you mean the portal I mentioned in an earlier post?
It's not quite ready. My previous reference was only meant to illustrate a UI
design that would be hard to duplicate under a UI framework like .Net. You'd
need to be able to think WAY outside the box.
What caused you to think of it as a "near term" solution? Or did you mean an
interim solution? If so, was it something I said?
My reason for asking is that I intend most my applications to be long-term
solutions, which is my reason for developing under the i5 native virtual
machine. I'm accustomed to my applications being used for 15+ years, which is
precisely my reason for not developing under an architecture like .Net.
However, do an app architecture like you are doing, even if you
don't build it at first with all the bells and whistles, will allow for
the addition of same, later...
I'm not sure I understand the grammer, but if you're asking whether my
architecture is extensible, and adaptable, I'd say yes, definately! In my
mind, extensibility, adaptability, performance, and scalability are the heart
of good design.
Touching a bit more on performance and scalability, if you have an application
server that supports say 500 requests per second, while another supports only
50 requests per second, the types of applications you can deploy under the
first can be more interactive. When users compare the alternative applications
side by side, they'll normally pick the first.
Of course, people who promote the second architecture will claim they can
handle a heavier load by installing a rack of servers and software to balance
the load across the entire rack. But those types of implementations are
expensive to deploy/manage and introduce more points of failure. Ironically,
which architecture would you say is most prevalent?
I'm trying to breathe new life into the platform by modernizing its
image, not keep in stuck in the past.
Same here. A lot of i5 developers link their careers (or what remains of them)
to the 5250 interface, but I've only written a few 5250 applications in the
past 10 years. The vast majority of my applications since 1997 have been
either thick-client or Web based, mostly Web.
The i5 has a good database, but the real value of the i5 is in application
serving, otherwise somebody has wasted a lot of money.
Nathan.
midrange.com
