Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
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.