Good News Everybody!
The new search engine is LIVE!
Please report any problems to david (at) midrange.com.
|
> From: Bartell, Aaron L. (TC) > > If you don't use an HTTP call with XML to an RPG-CGI program (web > services) > from your Java app how do you make it portable and loosely coupled? Too many buzzwords for me. For portability, I just use the Java Toolkit, and it runs on any platform with a JVM. Portability is a pretty well defined term: runs on different platforms. How I connect to the host is an implementation detail. But I have no idea what YOU mean by loosely coupled. Evidently, you consider HTTP communications using XML to communicate with an RPG program to be loosely coupled, but I don't agree. Why it has to talk to an RPG program is beyond me. If I'm communicating via HTTP, I may be talking to a servlet, not an RPG program. The servlet can invoke the RPG server. And why is an HTTP call with XML any less loosely coupled than a toolbox call to one of the OS/400 host servers? Maybe I want to use a serial connection. Or APPC, for security reasons. Unfortunately, you've tied me into TCP/IP with your tightly coupled web services design. Me, I'll just put a wrapper around the delivery class and reimplement it as needed, without having to touch my application. That's the point of OO design. Joe
This mailing list archive is Copyright 1997-2026 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.