RE: IIS to as/400 odbc -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: IIS to as/400 odbc
From: SCarter@xxxxxxxxxxx
Date: Wed, 15 Aug 2001 11:38:51 -0500
List-Archive: <http://archive.midrange.com/midrange-l/>
List-Help: <mailto:midrange-l-request@midrange.com?subject=help>
List-Id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-Post: <mailto:midrange-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>





>>

This depends on the amount of work you want to do.  A relatively simple
messaging protocol is not hard to implement, but you will have to write a
database server for each set of related files you wish to expose.  It's not
difficult, but it can be a lot of code.
>>

Ok now for the begging and pleading where can I get some information on
writing a messaging protocol (probably our favorite redbook 'Sorcerer's
guide').
And then how would I be set up access from our DMZ.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: IIS to as/400 odbc , Joe Pluta

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.