|
|
Posted by awebguynow on 10/04/37 11:36
I'm investigating this subject, particularly DB interactions, and could
use input.
It seems the dominant consensus, in these discussions is "use flock()
...."
I guess this would be similar to, in Java terms, using synchronized
(objLock) { ... }
This lends itself to OOP modularization, localization of reads and
writes, using locks.
Also, MySQL might say in the manual,
this storage engine locks at the [page | row | ...] level.
But what does this get you ?
If the goal is consistent data, and no simultaneous writes, its a
worthy goal.
But how should the application be designed ?
Do you limit access to reports, displays, forms on data that is
currently being written ?
If a PHP flock() or DB lock impedes access, what then ?
Does it wait a time slice then try ? or throw error ? fatal error ?
recover ?
Any good articles, references ? any from Wrox, O'Reilly ? TIA for
responses
Navigation:
[Reply to this message]
|