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
The current Transport interface does not seem suitable for transports that are not request-response oriented.
With HTTP, the correlation of request to response is part of the protocol. I have a project where I'm using a raw socket. Once I get a message, I need to still inspect it to see if the id of a response matches a previously sent request. So I end up having to decode to JSON anyway and so JSON decoding happens twice in the app.
I'm not sure of the best way forward.
The text was updated successfully, but these errors were encountered:
The current Transport interface does not seem suitable for transports that are not request-response oriented.
With HTTP, the correlation of request to response is part of the protocol. I have a project where I'm using a raw socket. Once I get a message, I need to still inspect it to see if the id of a response matches a previously sent request. So I end up having to decode to JSON anyway and so JSON decoding happens twice in the app.
I'm not sure of the best way forward.
The text was updated successfully, but these errors were encountered: