They are not buffered due to a lack of protocols which recognices
changes in the remote filesystem. A protocol which transfers all
changes in files may slow down the system dramatically, if
- the client is not as fast as the server
- the connection is very slow
- many clients using a server, all changes then must be transfered
vise versa
Furthermore this would cause a load on the client even it is not used.
My suggestions to solve this really nasty problem are the following:
- only on one client used filesystems (not used by the server)
could be cached (rarely used)
- caching of read only filesystems is possible (splitting into read
only part eg. /usr/* and a read-write part)
- introduce an cache protocol, working this way:
- whenever the client opens a file for reading, first there is
searched in the clients cache
- if found, the file dates are compared over network
- if equal use the clients cache
- if not transfer from server
- if not, transfer from server
- whenever the client opens a new file for writing, transfer
while closing
- whenever a file on the server is opened for appending or
read-write go the same way as opening for reading, transfer
it back while closing
....................DK
--
-------------------------------------------------------------------------------
Cyber Systems - Cyber Systems - Cyber Systems - Cyber Systems - Cyber
Systems
-------------------------------------------------------------------------------
Dieter K�ppel, Lanzenweg 11, 90455 N�rnberg
Phone: ISDN 0911-884857, GSM 0171-5247468, Login: ISDN/Modem
0911-883175
mailto:tires@nuernberg.netsurf.de
-------------------------------------------------------------------------------
Repairing - Updating - Workstations - Configuration - Server -
Terminals
-------------------------------------------------------------------------------
Cyber Systems - Cyber Systems - Cyber Systems - Cyber Systems - Cyber
Systems
-------------------------------------------------------------------------------