|
midrange-l-bounces@xxxxxxxxxxxx wrote on 06/20/2005 11:00:52 AM: > >There is a single, official way to get to the web on the iSeries: JSP > on > >WebSphere. > > OK. Then why is IBM spending money on HATS? On WebFacing? On iSeries > Access for the Web? And if these aren't "official" directions, then why > is IBM paying to send their people to user groups to teach about using > them? IBM, please, cut the crap and provide some direction. > > -Walden Given that all of the items you site are "applications" built on top of JSP and WebSphere, I am fairly confused as to why you see this as IBM not having a direction? In my opinion, these applications all reinforce the technical direction. They provide varying degress of quick migration built on top of the same technology that you could potentially rewrite your apps to fully migrate to. They also offer the possibility of reusing bits and pieces within custom WebSphere apps. For example, if you are writing a WebSphere (J2EE) app and have a need to provide access to something like spooled files in the browser, you do not have to write that yourself. Instead, you can leverage iSeries Acess for Web, just as your 5250 app leveraged WRKSPLF. Of course, other than only needing 1 server architecture vs. 2, there is nothing to stop you from reusing those same bits just as well from an ASP .NET app. Given the problem a lot of people seem to be having learning just one of these server architectures, that is probably not insignificant. Mark _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.