The UNIX domain sockets (UNIX pipes) are typically used when communicating between two processes running in the same UNIX machine. UNIX pipes usually have a good throughput. They are also more secure than TCP/IP, since UNIX pipes can be accessed only from applications that run on the computer where the server executes.
When using the UNIX Pipes protocol, you must reserve a unique listening name (server name) within the node for the server, for instance, “solidDB®”. Because UNIX pipes handle the UNIX domain sockets as standard file system entries, there is always a corresponding file created for every listened pipe. In solidDB®’s case, the entries are created under the path /tmp.
For example, the server name solidDB creates the directory /tmp/solunp_soliddb and shared files in that directory. The /tmp/solunp_ is a constant prefix for all created objects while the latter part (solidDB in this case) is the server name in uppercase format.
To use the UNIX pipes protocol, select upipe or unp as the protocol and enter a server name.
Where
Syntax example
Server
Listen = upipe server name
Client
Connect = upipe server name
▪To use the UNIX pipes protocol, the server and client processes must run in the same machine.
▪The server process must have “write” permission to the directory /tmp.
▪The client that is accessing UNIX pipes must have “execute” permission on the directory /tmp.