Connectivity Framework Annex D : Assessment Template : HTTP
D . 6.5 Implementation Viewpoint D . 6.5.1 System Architecture Considerations
Peer-to-Peer vs . Broker :
( Section 4.2.1.1 )
Data-Centric vs . Device / App-Centric : ( Section 4.2.1.2 )
Explicit vs . Implicit Governance : ( Section 4.2.1.3 )
D . 6.5.2 Data Considerations
Content-Based Selection ( Section 4.2.2.1 )
Time-Based Selection ( Section 4.2.2.2 )
D . 6.5.3 Performance Considerations
Real-Time ( Section 4.2.3.1 )
Latency and Jitter vs . Throughput ( Section 4.2.3.2 )
D . 6.5.4 Scalability Considerations
Data Objects ( Section 4.2.4.1 )
Apps ( Section 4.2.4.2 )
Does the connectivity framework require running a special process or broker ?
No , HTTP does not require running a special process or broker to communicate between the client and the server .
Does the application code ( or business logic ) have to be aware of the other endpoints in order to participate in information exchange ?
No , the client application code does not have to be aware of the server implementation details in order to participate in a data exchange . The server responses indicate the available resources and the methods allowed on them . Is the governance explicit and shareable ?
The governance is implicit , embedded in the request and response headers and data exchanged between a client and a server .
Can a content-filter specify the data subset of interest ?
No , HTTP does not provide a content filtering mechanism to specify a data subset of interest . However , it does support the concept of “ content negotiation ” between a client and a server . It is left to the server to define the results of the content negotiation . Can sub-sampling specify the data subset of interest ?
No , HTTP does not provide a sub-sampling mechanism to specify a data subset of interest .
Does the connectivity technology support real-time data distribution ? Is the latency deterministic ( smaller jitter is better )?
No , HTTP is not designed to support real-time data distribution . The latency is not deterministic . The use of TCP can result in unbounded latency and jitter . How does the latency and jitter change with throughput ? What limits the throughput ?
Latency and jitter can suffer as throughput increases . The throughput is limited by the message size , network bandwidth and available memory .
Can the connectivity framework effectively handle an increasing number of data objects ? What limits data object size ?
Yes , HTTP can effectively handle an increasing number of data objects . There is no inherent limitation on the representation size of a data object . A data object ( i . e . resource ) representation may be finite or may be unbounded .
Can the connectivity framework effectively support interface evolution for an increasing number of distributed application components ?
Yes , HTTP can effectively support interface evolution for an increasing number of distributed application clients , since the hypertext is used to decouple the clients from the server state . The hypertext response from a server defines its interface , and controls the resources and methods available to its clients .
IIC : PUB : G5 : V1.0 : PB : 20170228 - 99 -