|
I have a world of respect for Tim and what he's been trying to achieve
Vern, but having looked at the web client stuff I wouldn't spend any
more time on it unless they make major changes.
It is very limited and has only about 1/10th the capability of Scott's
HTTPAPI. As you noted, it requires the C compiler - which in turn
means that if anything goes wrong you stand little chance of fixing
it. With Scott's stuff, on the rare occasions when there is a problem,
you can debug it yourself as well as enlisting the help of the
community.
My take is the built-in server seesm to work well - I haven't tried to
deploy existing apps with it, but the web services generated by the
wizard that use your underlying RPG or COBOL is pretty good.
In my opinion though, the client side is not worth the effort except
for with clients who will not consider anything that doesn't say "Made
by IBM" on it. HTTPAPI by itself or in conjunction with WDSL2RPG do a
far better and more comprehensive job. This (the client side) is one
of those areas where I'd rather IBM spend its money on something else.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
On Nov 8, 2010, at 9:29 AM, web400-request@xxxxxxxxxxxx wrote:
Now to get the client working in RPG, you still need the C compiler.
Aaron, did you hear Tim's presentation at the Summit? He spoke of
several things around this - can't remember what's NDA at the moment!
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
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.