RE: Format of sqlhosts file

> -----Original Message----- > From: Graham Nicholls [mailto:graham@rockcons.co.uk] > Sent: Tuesday, May 24, 2005 8:27 AM > To: informix-list@iiug.org > Subject: Re: Format of sqlhosts file Snipped > The 3 fields are as follows: > > XX 2 character server type - "on" for IDS, and "se" for Standard engine. > > XXX 3 char for connection method. This can be "soc" for sockets, tli for > the old AFAIK only used on SCO Unix, "ipc" for interprocess communication. > Apparently "ipc" is unreliable, and since it it for local connections (ie > to > the same machine) it it of no practical use. I've never heard that ipcshm connections are unreliable. I think you'd find that the vast majority of Informix installations on UNIX or Linux where the clients and server run on the same machine are using it. This is especially true in installations where connection speed is important: it's much quicker to write data to a shared memory location, than to gather it, package it, send it to the loopback port (for a local connection), retrieve it, unpackage it and then allow the client to access it. The only real problem is that you can't use this protocol from a remote client; remote clients must connect by IP. --EEM sending to informix-list