uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <...@uima.apache.org>
Subject [jira] [Updated] (UIMA-6048) UIMA-DUCC: simplify pullservice protocol
Date Wed, 05 Jun 2019 18:42:00 GMT

     [ https://issues.apache.org/jira/browse/UIMA-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jerry Cwiklik updated UIMA-6048:
    Fix Version/s:     (was: 3.0.1-Ducc)

> UIMA-DUCC: simplify pullservice protocol
> ----------------------------------------
>                 Key: UIMA-6048
>                 URL: https://issues.apache.org/jira/browse/UIMA-6048
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Major
>             Fix For: future-DUCC
> Currently the pullservice uses 3 way protocol when communicating with a client (like
JD). Its GET, ACK, and END. Each requires a round trip from a pullservice to the client and
> It would be more efficient to remove the ACK, call GET once (to get initial task) and
just keep calling END which would do two things:
> Convey end of task (success or failure)
> Return new task to process
> The ACK was a carry over from the time when JMS (ActiveMQ) was used as transport and
it occasionally was loosing tasks. Its main function was to indicate which service (and thread)
was processing the task. HTTP seems more robust and the ACK is no longer necessary.
> To support the new protocol, JD needs refactoring to stop relying on ACK and also to
fetch a new task (or null) in response to END.

This message was sent by Atlassian JIRA

View raw message