You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Send & subscribe and subscribe transaction data providers should be implemented as part of the new WebSocket pub/sub system based on the [Draft design of new WebSockets] (#6508).
Requirements:
Send & subscribe and subscribe transaction data providers constructors should be implemented. The constructors should create a corresponding subscription.Subscription based on input arguments, and store topic, subscription and other necessary parameters in a newly created instance. These constructors should be called in a DataProviderFactory::NewDataProvider method.
Run should be implemented. It will start in a forever loop until the subscription is closed. This method collects streaming data from the subscription, similar to how we do it, for example in SendAndSubscribeTransactionStatuses:
Guitarheroua
changed the title
[Access] Add implementation TransactionStatusSubscriptionHandler for transaction status subscription
[Access] Add implementation for transaction status data provider
Nov 22, 2024
Guitarheroua
changed the title
[Access] Add implementation for transaction status data provider
[Access] Add implementation for transaction status data providers
Nov 29, 2024
Send & subscribe and subscribe transaction data providers should be implemented as part of the new WebSocket pub/sub system based on the [Draft design of new WebSockets] (#6508).
Requirements:
Send & subscribe and subscribe transaction data providers constructors should be implemented. The constructors should create a corresponding
subscription.Subscription
based on input arguments, and storetopic
,subscription
and other necessary parameters in a newly created instance. These constructors should be called in aDataProviderFactory::NewDataProvider
method.Run
should be implemented. It will start in a forever loop until the subscription is closed. This method collects streaming data from the subscription, similar to how we do it, for example inSendAndSubscribeTransactionStatuses
:flow-go/access/handler.go
Lines 1407 to 1451 in 3496c0f
Then the data is formatted in response messages for the client and written to the
send
callback.Also,
MessageIndex
should be included in the response.The
Close
method should be implemented to shut down the subscription gracefully.ID
andTopic
getters should returnUUID
and the topic respectively.The text was updated successfully, but these errors were encountered: