At 06:32 PM 10/09/2001 -0400, you wrote:
> > 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.
I'd never read that before Larry. Not saying you're wrong, just that the
only
references to caching I have read referred to not needing to read the disk
again for recently _read_ data.
Warmest regards,
Tom Grimshaw
coy: Just For You Software
tel: 612 9552 3311
fax: 612 9566 2164
mobile: 0414 675 903
post: PO Box 470 Glebe NSW 2037 Australia
street: 3/66 Wentworth Park Rd Glebe NSW 2037
email: [EMAIL PROTECTED]
web: www.just4usoftware.com.au
This email and any files transmitted with it are confidential to the
intended recipient and may be privileged. If you have received this email
inadvertently or you are not the intended recipient, you may not
disseminate, distribute, copy or in any way rely on it. Further, you should
notify the sender immediately and delete the email from your computer.
Whilst we have taken precautions to alert us to the presence of computer
viruses, we cannot guarantee that this email and any files transmitted with
it are free from such viruses.
