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 Mar 18, 2014, at 11:25 AM, Rafael Schloming wrote:
> 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 difficu
>>
>>
>> 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.
>>
BTW I don't need the javadoc.. just point me what class are you talking about
and I will figure out
On Tue, Mar 18, 2014 at 11:43 AM, Clebert Suconic wrote:
> On Mar 18, 2014, at 11:25 AM, Rafael Schloming wrote:
>
> > 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 do
On Tue, Mar 18, 2014 at 11:53 AM, Clebert Suconic wrote:
> >>
> >>
> >> 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.
> >>
>
> BTW I don't need the javadoc.. just point me what class are yo
>
>>
>> Right now my implementation is forced to cast to ConnectionImpl what
>> breaks the purpose of the interface. Can you guys move it?
>>
>
> I'm happy to accept a patch for it, although I'd encourage you to check out
> the events stuff in any case.
>
> --Rafael
I sure will take a look o
On Tue, Mar 18, 2014 at 2:23 PM, Clebert Suconic wrote:
> >
> >>
> >> Right now my implementation is forced to cast to ConnectionImpl what
> >> breaks the purpose of the interface. Can you guys move it?
> >>
> >
> > I'm happy to accept a patch for it, although I'd encourage you to check
> out
> >
