| Section |
|---|
| Column |
|---|
| Excerpt |
|---|
An IdentifyPillarsForGet IdentifyPillarsForGetFile conversation consists of an IdentifyPillarsForGetRequest IdentifyPillarsForGetFileRequest message and of a number of IdentifyPillarsForGetReply IdentifyPillarsForGetFileReply messages. |
When a client wants to use the Get File functionality to retrieve a file, it first needs to decide from which pillar to get the the file. This can be done with the IdentifyPillarsForGet IdentifyPillarsForGetFile primitive. This is not required, but it is the means to establish where to direct the Get.The client sends an IdentifyPillarsForGetRequest IdentifyPillarsForGetFileRequest message via the general topic for the SLA on the message bus to the concerned pillars, and the concerned pillars reply with IdentifyPillarsForGetReply IdentifyPillarsForGetFileReply messages via the client queue (specified in the IdentifyPillarsForGetRequest IdentifyPillarsForGetFileRequest message) on the message bus to the client. |
| Column |
|---|
|
|
...
See also Message exchange protocol
...
IdentifyPillarsForGetFileRequest
The IdentifyPillarsForGetRequest IdentifyPillarsForGetFileRequest always contains a DataID FileID such that the pillars know what data is requested. In future versions the message format be extended to allow more dataIDs FileIDs as a list, pattern or address.
...
The request contains credentials, such that the pillar can determine if access is allowed. The credentials are not yet specified in the xsd's.
...
IdentifyPillarsForGetFileReply
The reply always contains a PillarID, which is the ID of the queue, where the Get message can be directed to.
The reply also always contains a dataIDFileID, such that the client is sure the message concerns the right data.
...