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

API: Transaction history -to event stream- #4

Closed
spikeekips opened this issue Jun 1, 2018 · 2 comments
Closed

API: Transaction history -to event stream- #4

spikeekips opened this issue Jun 1, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@spikeekips
Copy link
Contributor

spikeekips commented Jun 1, 2018

(almost same with #3)

This api can be used to check how the transmitted transaction(from client) is finished,

  • tx gets consensus successfully?
  • or tx is failed because of some reason

  • If tx gets consensus successfully, the response will have BlockTransaction data.
  • If failed, the response will have BlockTransactionHistory data.
@spikeekips spikeekips added this to the Opening Testnet milestone Jun 1, 2018
@spikeekips spikeekips added the enhancement New feature or request label Jun 1, 2018
@kfangw
Copy link
Contributor

kfangw commented Jun 20, 2018

If a client get BlockTransaction or BlockTransactionHistory, there is no more data to be sent to the client i think.
Then, the server should drop the connection right?
@spikeekips

@kfangw kfangw changed the title API: Transaction history to event stream API: Transaction history -to event stream- Jun 20, 2018
@spikeekips
Copy link
Contributor Author

@kfangw : If a client get BlockTransaction or BlockTransactionHistory, there is no more data to be sent to the client i think. Then, the server should drop the connection right? @spikeekips

If not in 'event-stream', connection should be stopped by server-side, but in 'event-stream', the server and client should stay put in connection and wait for newly added transactions, is it make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants