I doubt there is a good reason, however I suspect the new events API would probably be an easier alternative to getWorkHead() and friends. Unfortunately there aren't docs for the Java version of the API yet, but it shouldn't be difficult to figure out how to use it from the C API docs.
--Rafael On Mon, Mar 17, 2014 at 12:44 PM, Clebert Suconic <[email protected]>wrote: > Why getWorkSequence is not exposed through Connection? > > > Forcing me to use getWorkHead() would make me re-implement the exact same > Iterator that's being implemented at ConnectionImpl(); Why not just expose > it properly? Iterators are common practice in Java anyways.
