I may appear as unwanted guest in this list.
But, what I feel is that the name should not cause any confusion among
community.

It is quite understood that as Oracle uses ORA, Microsoft uses MS as
prefix and everyone understands that. They what is wrong with XNET. Only
this is we will need one note mentioning that XNET is not a protocol.


Rakesh Shrivastav
Associate Consultant - Investment Banking Group
PrimeSourcing(tm), The Global IT Services Business from i-flex - "Add
Value Reduce Risk"
i-flex Solutions Limited - Mumbai
Tel Office: 91-22-5642-7000 Ext. 7136
Mobile : 91-9892803682
e-Mail: rakesh.shrivastav@...

:)) My favorite mythical creature? The honest politician :))


-----Original Message-----
From: Firebird-Architect@yahoogroups.com
[mailto:Firebird-Architect@yahoogroups.com] On Behalf Of Dmitry Yemanov
Sent: Thursday, October 06, 2005 12:06 PM
To: Firebird-Architect@yahoogroups.com
Subject: Re: [Firebird-Architect] XNet and Connect Strings

"Leyne, Sean" <Sean@...> wrote:

>
> "IPC" suggests the old local connection mechanism, but XNET is a
> completely different and better implementation.

To be precise, both transports are IPC (inter-process communication)
implementations and both work via the shared memory. The difference is
in
the details and in the layering. The one from Borland is known as
IPSERVER
code, the newer one is referred to as XNET. We here often used "IPC" to
refer the old implementation, but formally this is not correct. I agree
that
some confusion could happen, but I see nothing critical here.


Dmitry




Yahoo! Groups Links