|
Anything that doesn't have a published industry-standard syntax, Phil. It could be something as simple as sending SQL requests to a listener on a onon-standard port, but I personally prefer to use a message-based design where I have designed the protocol and nobody on the outside is likely to be able to hack it. One example is remote data queues, where an iSeries inside the firewall reads data queues on another iSeries outside the firewall, using SNA. Joe > -----Original Message----- > From: midrange-l-admin@midrange.com > [mailto:midrange-l-admin@midrange.com]On Behalf Of prumschlag@phdinc.com > Sent: Wednesday, August 15, 2001 8:16 AM > To: midrange-l@midrange.com > Subject: RE: IIS to as/400 odbc > > > > > Joe, > > If you don't mind educating a novice, could you explain what you mean by a > "proprietary protocol"? > > Phil
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.