Get data with id1 from fastest pillar

Owned by Bolette Ammitzbøll Jurik
Last updated: Jan 11, 2011Version comment
1 min read

... user requests data with id1 and gets access to data as fast as possible ...

This is all the user knows. The application (Get client) needs to find out where (which pillars) can deliver the data and how fast. The application then chooses who will deliver and specifies whereto (data token). When the data has been delivered, the user will be pointed to the data. The communication is in 4 steps:

  • who can deliver query from client to pillars in SLA
  • response from pillars
  • get request with data token from client to specific pillar
  • response in form of file exchange and reply messages

The detailed communications of a specific test case are described in Scenarie1 in which everything goes according to plan (there is a negative IdentifyPillarsForGetReply from one pillar, but the client can simply choose a different pillar and proceed with the GetRequest).