Entonces todo esto quiere decir que en mi ejemplo no habria forma de acceder
a los datos del archivo a menos que, como dijo Julio en el otro mensaje (y
al final de este), exista
NFS de por medio..... No me gusta pero es logico.
-----Mensaje original-----
De: Walter Castro <[EMAIL PROTECTED]>
Para: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Fecha: Domingo, 30 de Julio de 2000 01:08 p.m.
Asunto: [LUG.ro] RE: [LUG.ro] �Como lo hace X?
>X Windows is actually a series of pieces working together to present the
>user with a GUI:
>n The base window system is a program providing services to the X Windows
>system.
>n The next piece is a protocol for communicating across the network-the X
>Network
>Protocol.
>n On top of the program implementing the X Network Protocol is the
low-level
>interface,
>named Xlib, between the network/base system and higher-level programs.
>Application
>programs typically use functions in the Xlib instead of the lower-level
>functions.
>n Tying these pieces all together is a window manager. The window manager
is
>an X
>Windows application whose purpose is to control how windows are presented
to
>users.
>Different from most other window systems, the base window system doesn't
>provide user
>interface objects, such as scroll bars, command buttons, or menus. The user
>interface items
>are left to the higher-layer components and the window manager.
>What Is a Client/Server System?
>X Windows is a client/ser ver system controlled by two individual pieces of
>software with one
>piece running on the client and the other running on the server. The client
>and server pieces of
>this puzzle can be on different systems or, as is the case with most
>personal computers, both
>pieces can reside on the same machine.
>Client/server is one of the major buzzwords used in the computer industry
>today. Like most
>basic concepts in the industry, client/server has been overplayed and
>overused to the point of
>confusing the average computer user. In the traditional sense, a server is
a
>machine that just
>provides resources-disk drive space, printers, modems, and so on-to other
>computers over
>a network. A client is the consumer of these services-in other words, a
>client uses the disk
>space, printer, or modems provided by a server.
>Now that you understand what a client is and what a server is, it's time to
>reverse it all. In the
>world of X Windows, the client/server relationship is the opposite of what
>you've come to
>know in the PC world. The accepted or common notion of a server is that it
>provides services
>to a client who uses them. In the most basic form, a client displays the
>application that's run-ning
>on the server.
>Under X Windows, the server displays the application that's running on the
>client. This may
>seem a bit confusing at first, but it'll make sense when you become more
>intimate with the X
>Windows system.
>In X Windows, a client is the resource that provides the programs and
>resources necessary to
>run an application-what in the traditional sense would be called a server.
>The resources re-side
>on the client system (remember that the client and server systems can be on
>the same
>machine), whereas the application is displayed and interacted with on the
>server system.
>The capability of an X Windows application, which is the client, to run
>under a server located
>on either the same computer or on another computer is called network
>transparency. Thus, an
>X application doesn't care whether it runs on a local or remote machine.
>This capability can be
>used to run time-consuming tasks on another server, leaving the local
client
>unencumbered to
>perform other tasks.
>
>> -----Original Message-----
>> From: Julio Cesar Gazquez [SMTP:[EMAIL PROTECTED]]
>> Sent: Saturday, July 29, 2000 4:36 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: [LUG.ro] �Como lo hace X?
>>
>> Pablo Armando wrote:
>>
>> Suspenso... Las respuestas al final :-)
>>
>> > Si tengo una maquina A donde esta el programa xgraficos que es como un
>> corel
>> > :�)
>> > y tengo una maquina B donde estoy corriendo mi servidor X y donde tengo
>> > guardado
>> > un archivo de imagen de 50MB. Hasta ah� estamos.
>> >
>> > Ahora ejecuto xgraficos como un cliente en mi servidor X y le digo que
>> abra
>> > el archivo
>> > este de 50MB.
>> >
>>
>> B es simplemente la terminal desde donde interactu�s con el programa,
>> pero el programa corre en A, y el archivo en principio no est� en A. Por
>> tanto, vos no acced�s al archivo salvo que con NFS, SMB, Coda o alg�na
>> otra cosa veas los archivos de B desde A. El protocolo X se limita a
>> manejar la unidad de display (pantallas+teclado+mouse).
>> Es an�logo a trabajar con una terminal serie o por telnet... Vos "ves"
>> las cosas desde un puesto de trabajo, pero "trabaj�s" sobre el otro
>> equipo, como si estuvieras en su consola. Si no ten�s un medio expl�cito
>> de acceso al equipo donde vos est�s sentado desde el otro, es lo mismo
>> que si no existiese.
>>
>> > Espero que alguno de ustedes tenga una respuesta porque me estoy
>> volviendo
>> > loco!!!!.
>>
>> Supongo que ahora te vas a querer pegar un tiro...
>>
>> --
>> Saludos
>>
>> Julio C�sar G�zquez
