I am trying to avoid locking the access to file for multiple readers can be multi concurrent readers and it will be a bottleneck. I've created a multi threaded test for it and it seems to work fine, but I am not still not confident about it. I was hoping to find some documentation about it which specifies the behavior.
On Dec 20, 11:40 pm, Christian Catchpole <[email protected]> wrote: > Can you even get a second lock on a file that way? Sounds dangerous. > I would just create a some kind of service that each Thread can access > that will synchronise disk access down to one RandomAccessFile. > > On Dec 21, 2:48 am, Eitan <[email protected]> wrote: > > > I want to use a file in a single process with single writer or multi > > readers mutual exclusion, for that purpose I use number of > > RandomAccessFile instances over the same file which are open in read > > mode and are used concurrently. I also have a single RandomAccessFile > > open in "rw" mode which updates the file (not when it is being > > actively read). > > I do not close the Random Access File handles at any point. > > > I wanted to know if the data which is being written to the file with > > the RandomAccessFile in rw mode will always be visible to the readers > > after the the write is complete? > > (I am not using rws mode for performance issues, only for these > > readers which are in the same process). > > > Thanks > > Eitan -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
