Re: XMLSERVICE with .Net

Nathan,

Geez, such a heated debate over such a small thing. As Jon pointed out, I work for a company in the business of helping IBM I developers in creating web content via open access and RPG. I would never imply that there is anything inherently wrong with CGI or the HTTP server in general. Our products run 100% on the i using that same webserver.

I was simply explaining the process as I remembered it being explained to me by Tony at IBM. That was several versions ago (a year has passed since the discussion I believe so if I misstated the reasoning, I apologize). In any case, he is the primary developer in the project and also the one who put in the recommendation of using the stored procedure interface for production workloads. I see Alan has passed this thread on to him so I will let him address it.

Brian May
IBM i Modernization Specialist
Profound Logic Software
http://www.profoundlogic.com
937-439-7925 Phone
877-224-7768 Toll Free


              



-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Monday, August 06, 2012 8:46 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] XMLSERVICE with .Net

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.

--
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.