| Table of Contents |
|---|
Description
The scenario is: Get Part of File
This scenario is an extension of the first test scenario. Here the client gets part of a file. It could for example be
| Excerpt |
|---|
... user requests the first couple of minutes of a longer video file |
The scenario should start with an IdentifyPillarsForGet conversation (Step1 in scenario 1) (again not required, but best behaviour and a better starting point for the client as it then knows the currently best place to ask for the file). Only the Get conversation between client and Pillar2 (assumed to be fast) is described.
- (2a) specific GetRequest from client to specific pillar
- (2b) answer in form of data transmission
Illustrations to come. The following is concrete values in the general message format and in XML.
Get Conversation (Step 2 a+b)
Message 2a
Message is sent on 'Pillar2 Queue'.
Message 2a in general format
Element Name | Client1 |
!MessageName | GetRequest |
!ConversationId | scen3 |
!PillarIds | pillar2 |
!DataIds | Id1 |
!ReplyQueueName | undefined |
Token | http:/a/b.data |
Synchronous | undefined |
Offset | 0 |
Size | 4096 |
Message 2a in XML format
| Code Block |
|---|
<message>
<MessageName>GetRequest</MessageName>
<conversationId>scen3</conversationId>
<pillarIds>
<pillarId>pillar2</pillarId>
</pillarIds>
<dataIds>
<dataId>Id1</dataId>
</dataIds>
<token>http:/a/b.data</token>
<offset>0</offset>
<size>4096<size>
</message>
|
Data Transmission 2b
...
and gets access to part of a file ... |
| Child pages (Children Display) | ||||||
|---|---|---|---|---|---|---|
|