Re: XMLSERVICE with .Net -- WEB400

Subject: Re: XMLSERVICE with .Net
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Mon, 6 Aug 2012 06:46:13 -0700 (PDT)
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

From: Thorbjørn Ravn Andersen
I may misunderstand the point, but isn't such a job the bare minimum
required for providing an SQL tunnel across the network and the task
of that job is to allow talking directly to the database?

It sounds like you get the point. There is a "tunnel" which includes ODBC Drivers and QZDASOINIT Jobs. And even QZDASOINIT jobs use some some sort of interface comparable to SQL CLI under the covers for talking to the database.

But I was asking Brian. He was the one making a point of XMLCGI and it's SQL CLI interface being a "tunnel" with extra overhead, vs "talking directly with the database".

-Nathan.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: XMLSERVICE with .Net , Brian May

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.