OK. Let's assume that this is needed.
I think that an iterable interface on VectorWritable that throws UnsupportedOperationException or similar if you try to get the iterator twice is much more transparent than a watcher structure and much easier for a user to discover/re-invent. Another (evil) thought is a parallel class to VectorWritable which is essentially SequentialAccessVectorWritable that supports reading and writing. It seems to me that the Writable isn't real compatible with this interface in any case. How will that be resolved? On Mon, Dec 13, 2010 at 11:36 AM, Dmitriy Lyubimov <[email protected]>wrote: > Absent of this solution, i realistically don't see how i can go without a > push technique in accessing the vectors. >
