Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating approach to implementation BP Real-time access #396

Merged
merged 1 commit into from
May 13, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions bp.html
Original file line number Diff line number Diff line change
Expand Up @@ -2972,7 +2972,12 @@ <h4 class="subhead">Intended Outcome</h4>
</section>
<section class="how">
<h4 class="subhead">Possible Approach to Implementation</h4>
<p>Real-time data accessibility may be achieved through two means: </p>
<p>A possible approach to implementation is for publishers to configure a Web Service that provides a connection so as real-time data is received by the web service it can be instantly made available to consumers by polling or streaming. </p>

<p>If data is checked infrequently by consumers, real-time data can be polled upon consumer request for the most recent data through an API. The data publishers will provide an API to facilitate these read-only requests.</p>

<p>If data is checked frequently by consumers, a streaming data implementation may be more appropriate where data is pushed through an API. While streaming techniques are beyond the scope of this best practice, there are many standard protocols and technologies available (for example Server-sent Events, WebSocket, EventSourceAPI) for clients receiving automatic updates from the server.</p>
<!--<p>Real-time data accessibility may be achieved through two means: </p>
<ul>
<li> Push - as data is produced, it is communicated to
the data publisher either directly or by storage in a location accessible to the data publisher.</li>
Expand All @@ -2983,7 +2988,7 @@ <h4 class="subhead">Possible Approach to Implementation</h4>
<p>To engender greater credibility, in addition to data itself, publishers can provide access to
error conditions, anomalies, and instrument "house keeping" data. This will
enhance real-time applications' ability to interpret and convey
real-time data quality to consumers.</p>
real-time data quality to consumers.</p> -->
<aside class="example">
<p><a href="dwbp-realtime-example.html">Example page</a> showing an API specification for real-time data.</p>
</aside>
Expand Down