On Wed, Dec 1, 2010 at 12:26 PM, Bastian Blank
<email address hidden> wrote:
> The support for shared blob storage in ClientStorage assumes that it can
> read the blobs always. However if the blob directory is mounted via a
> network filesystem like NFS, it races against the cache on the client
> and server and can try to access it before the file creation was pushed
> through. At least for reading the ClientStorage should be prepared to
> retry to the load via the zodb connection if it can't read it directly.
Is this a case where one client was writing and a client on a different
machine was reading?
The notion of that you'd need to poll the blob data is disturbing.
On Wed, Dec 1, 2010 at 12:26 PM, Bastian Blank
<email address hidden> wrote:
> The support for shared blob storage in ClientStorage assumes that it can
> read the blobs always. However if the blob directory is mounted via a
> network filesystem like NFS, it races against the cache on the client
> and server and can try to access it before the file creation was pushed
> through. At least for reading the ClientStorage should be prepared to
> retry to the load via the zodb connection if it can't read it directly.
Is this a case where one client was writing and a client on a different
machine was reading?
The notion of that you'd need to poll the blob data is disturbing.
Jim
-- www.linkedin. com/in/ jimfulton
Jim Fulton
http://