Hi All,
In my view, reads should be able to occur simultaneously, but writes should be serialized and cannot occur when a read is taking place on the same record.
The thing is, if two reads are taking place at the same time on different records (this should be theoretically fine), there is only one file stream, which would mean, the two different reads would corrupt each other by trying to get information from different parts of the same file at the same time.
Synchronizing all data access methods is not something I want to do as it means all requests must occur in serial which basically defeats the point of concurrent access as the whole data class needs to be locked down for a simple read... which I think is pretty bad.
I can see that a better way would be that each
thread maintain there own connection (stream) or a concept of a stream pool be maintained by the database.
Does anyone have any comments on this? Am i taking this too far? Or am I making sense?
Thanx for any comments or help...
James.
[ October 07, 2004: Message edited by: James Turner ]
[ October 07, 2004: Message edited by: James Turner ]