[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xougen] RE: [Xouvert-general] Network transparentcy and modules

From: Jonathan Walther
Subject: Re: [xougen] RE: [Xouvert-general] Network transparentcy and modules
Date: Sat, 23 Aug 2003 01:50:12 -0700
User-agent: Mutt/1.5.4i

On Fri, Aug 22, 2003 at 02:57:23PM -0700, David Ross wrote:
Somebody correct me if I am wrong as it has been a long time since I
have done socket programming but a socket act very similar to a file and
if the socket is local on  a computer then all of the socket's
transactions take place in memory.  Again if memory serves me, but what
you put in on one side shows up on the other, hence a pipe.  It seems to
me that the system resources used are rather minimal and benefits rather
substantial.  This help reinforce code/product abstraction by forcing us
to decide what should be implemented server side and thus available to
everyone compared with what should be implemented client side.  Two of
the biggest beneficiaries of this methodology is security and stability
of the server.

Also, in the words of Mike Gancarz, the Unix Way is to keep kernels
small and minimal.  The X server counts as the "kernel" of an X11
"distribution".  So it is important to only put things in the server
that NEED to be there.  If it doesn't need to be there, then it is
better as a client-side library.



It's not true unless it makes you laugh, but you don't understand it until it makes you weep.

                    Geek House Productions, Ltd.

 Providing Unix & Internet Contracting and Consulting,
 QA Testing, Technical Documentation, Systems Design & Implementation,
 General Programming, E-commerce, Web & Mail Services since 1998

Phone:   604-435-1205
Email:   address@hidden
Webpage: http://reactor-core.org
Address: 2459 E 41st Ave, Vancouver, BC  V5R2W2

Attachment: pgpw2U4o6hE4E.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]