Read Process
The full sequence of events for a client, eg. read a file through Palisade, is as follows:
- A client will connect to the Palisade Service and receive a token.
- This token will be used to connect to the Filtered-Resource Service and receive many resources (and metadata for each resource).
- The client may choose to do some filtering on this metadata for only the resources they are interested in.
- Each resource is then read from the Data Service, returning a stream of serialised bytes (which the client may then further deserialise etc.).
Client Sequence Diagram
The above diagram shows the sequence of messages from the client's point-of-view, hiding the internals of the Palisade system. This can be considered as the 'API' for Palisade.
System Control-Flow Diagram
The above diagram shows the flow of control for a single request through the Palisade system.
Note the top-left trio of Client xxx Request nodes, each showing one of the interactions the client makes with the system (to the Palisade, Filtered-Resource and Data Services).