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
As discussed here it would be nice to add the feature of a virtual stream interface.
The reason is, that binance allows a max length of 8004 chars in the websocket URL. So if the coder creates a stream with a longer URL, the API should splitt the URLto chunks smaller than 8004 chars and create as much streams as needed. This streams should still be managed like one normal multiplex stream through the virtual_interface, so the coder does not have to care or to be aware of this.
The text was updated successfully, but these errors were encountered:
As discussed here it would be nice to add the feature of a virtual stream interface.
The reason is, that binance allows a max length of 8004 chars in the websocket URL. So if the coder creates a stream with a longer URL, the API should splitt the URLto chunks smaller than 8004 chars and create as much streams as needed. This streams should still be managed like one normal multiplex stream through the virtual_interface, so the coder does not have to care or to be aware of this.
The text was updated successfully, but these errors were encountered: