Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Flush why not flush?
Message
De
04/02/2003 12:46:13
 
 
À
04/02/2003 10:57:38
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00748117
Message ID:
00748946
Vues:
38
I'm not Tom but I'll give you an answer...

remember, the talk is about disabling WRITE CACHEING.

When WRITE cacheing is enabled, then the operating system, be it a server or a workstation, will tell your program that the WRITE is completed successfully EVEN THOUGH IT HAS NOT yet been physically written to the HD device. In effect it is lying to the application in anticipation that it will not encounter any difficulty when it gets around (usually very quickly) to actually instructing the HD to WRITE the bytes and receiving a response from the HD that all went well.

So, to answer your question, disabling write cacheing does NOT prevent buffering, either in the OS or in the HD. The written block(s) can still be buffered, but they will only be so once they have been physically written successfully. And of course READ blocks will be buffered as usual.

I'm no longer in contact with network administrators, but when I was they NEVER enabled WRITE CACHEING. Ever!!!

cheers

>What would the affect be on the VFP buffered data if write caching were disabled on the server. Would it be unable to buffer data.
>
>Miles
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform