On a Windows system, named pipes are supported using
standard file operations (no need for jcifs). The "file"
name for a named pipe is in the format
\ServerName\pipe\PipeName A local pipe (runs at
kernel level without all of the pipe overhead) is
The big speed advantage of using named pipes can only
be obtained when using local named pipes as TCP/IP is a
more efficient network protocol. jcifs does not and will
not support local named pipes (per response I received
from the developers).
I think it should be a simple matter in jTDS to look at
the host, if it is a period, do a file open instead of a
socket or jcifs open.