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
I guess lack of file size limits is an obvious example, but HTTP could just as easily be extended.
I was looking to use the socket concurrently, it looks like with this implementation the sending of unrelated Text and Binary frames would be ill-advised. Adding this wouldn't cost much, given the overhead of WS. Add in magic numbers. { name : is 0x7b206e616d65203a for example. For binary frames the server could send a generated or static magic number to prefix every binary frame.
The text was updated successfully, but these errors were encountered:
I guess lack of file size limits is an obvious example, but HTTP could just as easily be extended.
I was looking to use the socket concurrently, it looks like with this implementation the sending of unrelated Text and Binary frames would be ill-advised. Adding this wouldn't cost much, given the overhead of WS. Add in magic numbers.
{ name :
is 0x7b206e616d65203a for example. For binary frames the server could send a generated or static magic number to prefix every binary frame.The text was updated successfully, but these errors were encountered: