On Apr 1, 2005 9:10 AM, Helen Borrie <helebor@...> wrote:

>
> At 08:21 AM 1/04/2005 +0200, you wrote:
>
> >On Mar 31, 2005 3:02 PM, Helen Borrie <helebor@...> wrote:
> > >
> > > At 02:31 PM 31/03/2005 +0200, Daniel Albuschat wrote:
> > >
> > > >\\servername\C:\Program Files\Foo.fdb is a *local* path for FB,
> > >
> > > No, it is a remote path for a Named Pipes client attaching to a server that
> > > is *not* local.
> >
> >Uhm, I'm sorry. I didn't know about the Named Pipes "protocol".
> >But this sounds rather confusing, since named pipes have nothing to do
> >with networking in the first place.
>
> Really?????

Yeah well, if I hear "named pipes", I think of `man 3 mkfifo', which
creates pipes
that reside on a local filesystem only.
But you can, of course create an application that translates the data
read/written
to it's named pipe(s) to network traffic... It seems npfs does such a thing.

> >I couldn't find any infos about firebird
> >and named pipes via google... can you describe how firebird realizes
> >this named pipes thingie?
>
> Firebird doesn't "realize" Named Pipes.
> It's part of Windows networking
> services. The driver is called npfs.sys ("Named Pipes File Server" - Named
> Pipes actually is realized as a filesystem!) MySQL, MSSQLServer, Oracle
> (and many other applications) use it too. (Other NOSs have Named Pipes
> transports: it's not exclusive to Windows networking...)
>
> Firebird's default named pipe is called "interbas". It identifies the
> named pipes transport channel for the firebird service, much like the port
> number does for TCP/IP communications.

I see. Well, it's not entirely clear to me how this actually works.
Google's not very helpful today, either, but I guess I just bear with it,
it's rather off-topic anyways. :)

Thanks for the info,
Daniel

--
eat(this); // delicious suicide