Comments (2)
I agree that we should add reason
to the response from the [GET] /status
call.
For errors that may occur, I think it is on each individual Transmitter to handle as they see fit. We do have a StreamUpdated
event that allows the Transmitter to update the status of a stream without a request from the Receiver. This event includes a reason
that could be stored in the same place as the reason
data from a Receiver-driven status change, and reported in the same way from a [GET] /status
call.
We may have to think about how #56 impacts the reason
in a [GET] /status
response. That is, if the stream status is disabled but the stream's subject status is enabled, then we need to return "disabled" with the stream's reason
value.
from sharedsignals.
Closed by #86
from sharedsignals.
Related Issues (20)
- CAEP spec has subject in the examples
- Allow Receiver to supply public key HOT 9
- Mark fields optional or required in StreamConfiguration
- Push based- Incorporate Server-Sent Events (SSE) HOT 4
- SSF: Example of Stream Creation Response
- SSF: Example of Update Stream Status Response
- Stream creation lanaguage imply that transmiter must suport the poll delivery method if delivery method is not specified HOT 1
- The examples for stream update requests should not include Transmitter-Supplied fields in the request HOT 3
- Get stream status API response should include stream_id for consistrency HOT 1
- Update IANA considerations and well-known reference
- Update CAEP & RISC Events and SSF Docs with txn claim HOT 1
- Explore machine reachable approach to event definitions HOT 4
- Attacker Stream Subject Insertion
- Stream Audience Mix-Up
- Issuer Mix-Up
- Specify expected default behavior of streams with no subjects HOT 4
- Scanning for RISC API transmitters
- Initial security audit feedback HOT 1
- Clarify that only one event is allowed per SET HOT 4
- Clarify expected response when "state" is incorrect for Verification event HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sharedsignals.