Difference between revisions of "Data Transfer Common Messaging"
From Gcube Wiki
(Created page with '= Common Messaging Interface =') |
(→Common Messaging Interface) |
||
| Line 1: | Line 1: | ||
= Common Messaging Interface = | = Common Messaging Interface = | ||
| + | <br> | ||
| + | The Common Messaging Interface has been implemented so that messaging can be integrated from other Components such as scheduler and agent service. | ||
| + | <br> | ||
| + | === Messages === | ||
| + | <br> | ||
| + | *TransferRequestMessage: | ||
| + | This message holds information about the transfer details that usually scheduler sends to agent service. Information provided can be input uri's, destination folder, transfer options etc. | ||
| + | *TransferResponseMessage: | ||
| + | On the other side the transfer response message holds details about the submitted transfer. The transfer response message will be sent until the transfer has been completed (whatever that status be) and the receiver is able to see the bytes that have been transferred the status etc. | ||
| + | <br> | ||
| + | === Scenario === | ||
| + | <br> | ||
Revision as of 16:27, 18 March 2013
Common Messaging Interface
The Common Messaging Interface has been implemented so that messaging can be integrated from other Components such as scheduler and agent service.
Messages
- TransferRequestMessage:
This message holds information about the transfer details that usually scheduler sends to agent service. Information provided can be input uri's, destination folder, transfer options etc.
- TransferResponseMessage:
On the other side the transfer response message holds details about the submitted transfer. The transfer response message will be sent until the transfer has been completed (whatever that status be) and the receiver is able to see the bytes that have been transferred the status etc.
Scenario
