1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
TITLE="tuXlab Cookbook"
11
HREF="index.html"><LINK
13
TITLE="Thin-client computing"
14
HREF="c567.html"><LINK
17
HREF="x928.html"><LINK
20
HREF="x974.html"></HEAD
31
SUMMARY="Header navigation table"
56
>Chapter 6. Thin-client computing</TD
80
>Every solution will have some drawbacks, and a tuXlab is no
81
exception. I'll just mention a few in passing.</P
88
>Unreal Tournament will be lethargic or lag in response
92
>Graphics-intensive applications such as games will not
93
perform well, as all the display information will have to be pushed
94
over the network by the server. This is hundreds of times slower
95
than driving a local graphics card. Playing action games, however,
96
is not a goal of the tuXlab project.</P
99
>All the clients run the same
106
>Since it's really only one instance of Linux serving all the
107
desktops and applications, all the clients in the lab will
108
necessarily offer a Linux environment. It is possible for the
109
server to run software such as Wine (which enables many Windows
110
programs to run under Linux) or VMWare (which allows the server to
111
run instances of other operating systems), but in these cases the
112
underlying system will still be Linux, and the server will still be
113
doing all the work.</P
116
>Single point of failure</DT
119
>While it's very convenient that the thin-client workstations
120
are interchangeable and that you can access your desktop from
121
anywhere, it does mean that a catastrophic failure of the server
129
> client workstations out of
140
SUMMARY="Footer navigation table"
b'\\ No newline at end of file'
added
removed
lore/x956.html
