How else could you explain a lag of several minutes before system B can (in
some cases) see changes made by system A? It makes no sense to me unless I
view it in terms of two distinct caches (or I am particularly near-sighted
and cannot see the obvious answer, which is, of course, quite possible).
In the particular observed case, system A is a desktop machine and system B
is a thin client attached to a W2k server running Metaframe.
> > What got me to thinking about the caching was evidence such as User A
> > making a change to the data that it would take several minutes for User B
> > to see. I know this is not an R:Base problem, but if A's writes are being
> > cached, it will take B longer to see the change. Of course, B's reads are
> > also being cached by the controller, so the read cache would take even
> > longer to be updated with A's write. One must trust that the controller
> > will handle the refresh of the read cache given the now-immediate write.
>
>This isn't the way disk caching is _supposed_ to work. If the write is
>cached on the server, a read of that page of the database should find the
>one in cache rather than the one on disk.
>--
>Larry
