--===============0724383464==
Content-Type: multipart/signed;
  boundary="nextPart2235844.aZ7V0sv9yl";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2235844.aZ7V0sv9yl
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 11 February 2005 03:10, Thiago Macieira wrote:
> Jason Keirstead wrote:
> >No UNIX sockets is for sure a bad thing in WIn32.  But it is nothing you
> > could not work around ( look at Java - there are many JDBC drivers, for
> > instance, that will use a UNIX socket when in use in UNIX, and a TCP
> > socket when in use in Windows (when you are making a local DB
> > connection of course) ).
>
> True, I had thought of that. But, applications and libraries expect to
> give sockets whatever names they want. That will most surely have to
> change.
>
> Also, Unix sockets have a built-in protection mechanism due to filesystem
> paths. No one but root and the owner can access /tmp/kde-$USER. With
> AF_INET sockets, there's no such protection.

That's not a portable assumption. It's the behavior on Linux, but other UNI=
X=20
systems may not follow file system restrictions so it should not be relied=
=20
upon.

Cheers,
Waldo
=2D-=20
bastian@kde.org   |   Free Novell Linux Desktop 9 Evaluation Download
bastian@suse.com  |   http://www.novell.com/products/desktop/eval.html

--nextPart2235844.aZ7V0sv9yl
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBCDOtgN4pvrENfboIRAk61AJ9ecH/KFvO411sBbsA1i+NrpK7pDQCfdIg8
8QFF0yBLDtG750nsVGZtgDM=
=iJqZ
-----END PGP SIGNATURE-----

--nextPart2235844.aZ7V0sv9yl--


--===============0724383464==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============0724383464==--