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
Currently all the JSON-marshaled messages are encoded to base64 and then these messages are decoded from base64 and marshalled back to JSON. This takes time and has performance overhead. On the other hand, different message types might have different fields that might be bytes (binary value). This should be investigated to see if we can remove this encoding/decoding altogether and pass the data as v1.Struct (as a JSON object) without all the hassle.
The text was updated successfully, but these errors were encountered:
Currently all the JSON-marshaled messages are encoded to base64 and then these messages are decoded from base64 and marshalled back to JSON. This takes time and has performance overhead. On the other hand, different message types might have different fields that might be bytes (binary value). This should be investigated to see if we can remove this encoding/decoding altogether and pass the data as
v1.Struct
(as a JSON object) without all the hassle.The text was updated successfully, but these errors were encountered: