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
When the frontend receives a new message notification (with the message ID),
it performs a GET query to the API to download the received message.
Could you explain the reasoning behind this? Why not just send the message
itself via websocket? İ'm also considering using this design but İ can't find a reasoning
not to do the other way.
The text was updated successfully, but these errors were encountered:
So, as I understand, you want to make use of HTTP stuff while transferring data to client. But in the context of "transferring data" only, do you know if there are other implications? For example, which way is more likely to ensure consistent flow of data, e.g., order of messages.
And how about security & server load? I'm trying to figure out the best practice on this. Thanks!
Its indicated that:
Could you explain the reasoning behind this? Why not just send the message
itself via websocket? İ'm also considering using this design but İ can't find a reasoning
not to do the other way.
The text was updated successfully, but these errors were encountered: