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
For better performance on API servers, with #725 we introduced a new enable-subscribe-to-all option to the application, by default disabled, which means API clients (E.G. wallets) will be unable to subscribe to universal object creation and removal events by default.
However, as discussed in bitshares/bitshares-ui#1338, currently the reference wallet does subscribe to universal object creation and removal events. It may need some time for them to change, so we may need to keep the old behavior for longer time to avoid breaking things.
Note: we still want to change the default behavior in the future. So I think the best solution now is to
temporarily remove the new enable-subscribe-to-all option from configuration_file_options, and
set default value of application_options::enable_subscribe_to_all to true.
If this change is done, we need to create another ticket (issue) for reverting it in the future.
The text was updated successfully, but these errors were encountered:
For better performance on API servers, with #725 we introduced a new
enable-subscribe-to-all
option to the application, by default disabled, which means API clients (E.G. wallets) will be unable to subscribe to universal object creation and removal events by default.However, as discussed in bitshares/bitshares-ui#1338, currently the reference wallet does subscribe to universal object creation and removal events. It may need some time for them to change, so we may need to keep the old behavior for longer time to avoid breaking things.
Note: we still want to change the default behavior in the future. So I think the best solution now is to
enable-subscribe-to-all
option fromconfiguration_file_options
, andapplication_options::enable_subscribe_to_all
totrue
.If this change is done, we need to create another ticket (issue) for reverting it in the future.
The text was updated successfully, but these errors were encountered: