I am developing an application now (for nurses who care for home bound patients) that has many of these same issues. This trip has been very useful in orienting me to what some of the problems are. We will need a good caching strategy so it appears to the user of the application as if they never leave then net. For this application I think I know how to do that ... but it must be done.
I will look into AFS. Thanks for the tip, BobLQ On 12/18/06, Gregory K. Ruiz-Ade <[EMAIL PROTECTED]> wrote:
On Dec 17, 2006, at 1:33 AM, Andrew Lentvorski wrote: > AFS really wasn't meant for online/offline operation. It was > really meant to bond together sites connected with slow, unreliable > leased lines. The lines would go up and down but rarely remained > disconnected for extended lengths of time. Additionally, AFS is a royal PITA to set up, requiring at least three servers for the critical infrastructure. Also, AFS at some point apparently changed from caching whole files to caching file blocks, so your cache may not include a single whole file, depending on usage patterns of the filesystem. We keep looking at AFS as a possible replacement for NFS (we're looking for security, accountability and reliability), but every time we start probing AFS, it seems we're better off just dealing with NFS's failings than contorting our entire network around AFS. Gregory -- Gregory K. Ruiz-Ade <[EMAIL PROTECTED]> OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
