|
>Too many buzzwords for me. HTTP - HyperTextTransferProtocal XML - eXtensible Markup Language RPG-CGI - Report Program Generator-Common Gateway Interface Web Services - A program available through HTTP communication that uses XML as its data transport. Just for your notes when you decide web services are a good thing:-) >For portability, I just use the Java Toolkit, and it runs on any platform with a JVM. Scratch portability from that sentence, my mistake. By doing the above you are tied to the iSeries platform. That is why it is loosely coupled if you just offer a service with any language over HTTP with XML as the data transport. Then your Java servlet that is making use of the service doesn't care that it is on an iSeries, it just cares about the URL and the formats going in and out. <Joe> 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. </Joe> A web service can be written in any language, you are missing my point. <Joe> 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. </Joe> There are secure ways to transfer data with web services, try SSL over HTTP (HTTPS). <Joe> 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> That is a perfectly acceptable way to write it, say with interfaces, but you will have to write a new interface implementation every time a you move that servlet to another platform and try to use it's own method of communication. HTTP and XML are relieving the programmer from having to know how every other platform in the world works. Check out http://www.w3schools.com and read up on some of the technologies included there. Pay special attention to the following: http://www.w3schools.com/wsdl/default.asp http://www.w3schools.com/soap/default.asp http://www.w3schools.com/xml/xml_http.asp Hope that helps, Aaron Bartell -----Original Message----- From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx] Sent: Wednesday, September 03, 2003 5:02 PM To: 'Web Enabling the AS400 / iSeries' Subject: RE: [WEB400] Re: Modify the IE Browser > 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 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.