[
https://issues.apache.org/jira/browse/UIMA-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-5755:
--------------------------------
Description:
Pull service uses a three-way protocol to communicate with its client/driver.
It sends GET, followed by the ACK and END. The GET asks the client for a task
(CAS), the ACK confirms service receipt of it, and END indicates the task
completion.
To complete a task, a client may need a correlation Id to locate the task in
its database. Modify the protocol handler API to allow for user code to attach
the correlation ID and include it in a reply. The pull service should echo this
correlation Id in subsequent ACK and END messages.
Modify TAS callbacks onTaskSuccess() and onTaskFailure() to include correlation
object. Also the getSerializedCAS() method should somehow return the
correlation object along with a serialized CAS.
was:
Pull service uses three-way protocol to communicate with its client/driver. It
sends GET, followed by ACK and END. The GET asks the client for a task (CAS),
the ACK confirms service receipt of it, and END indicates the task completion.
To complete a task, a client needs a correlation Id to locate the task in its
database. Modify the protocol handler API to allow for user code to attach the
correlation ID and include it in a reply. Perhaps the best place is the
HttpResponse header. The pull service should echo this correlation Id in
subsequent ACK and END messages. This time by attaching it to HttpRequest
header.
Modify TAS TaskConsumer class to include correlationId.
> UIMA-DUCC: Pull service should echo correlation id in ACK and END msgs
> ----------------------------------------------------------------------
>
> Key: UIMA-5755
> URL: https://issues.apache.org/jira/browse/UIMA-5755
> Project: UIMA
> Issue Type: New Feature
> Components: DUCC
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Major
> Fix For: 2.2.3-Ducc
>
>
> Pull service uses a three-way protocol to communicate with its client/driver.
> It sends GET, followed by the ACK and END. The GET asks the client for a task
> (CAS), the ACK confirms service receipt of it, and END indicates the task
> completion.
> To complete a task, a client may need a correlation Id to locate the task in
> its database. Modify the protocol handler API to allow for user code to
> attach the correlation ID and include it in a reply. The pull service should
> echo this correlation Id in subsequent ACK and END messages.
> Modify TAS callbacks onTaskSuccess() and onTaskFailure() to include
> correlation object. Also the getSerializedCAS() method should somehow return
> the correlation object along with a serialized CAS.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
