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
Related to #86 we should also accept image data as mult-part form params which can be replaced in the JSON representation. Bundling base64'd image data blobs in JSON can be a pain. The previous format would still be accepted.
I'm thinking that ImageViewData's ImageData could have identifiers related to the form blocks.
Then a second block/boundary called checkOne with the encoded image data. The HTTP server would replace that data directly into the ImageViewData struct. We could try base64 decoding this data.
The text was updated successfully, but these errors were encountered:
Related to #86 we should also accept image data as mult-part form params which can be replaced in the JSON representation. Bundling base64'd image data blobs in JSON can be a pain. The previous format would still be accepted.
I'm thinking that
ImageViewData
'sImageData
could have identifiers related to the form blocks.The block containing JSON would be named
file
.Then a second block/boundary called
checkOne
with the encoded image data. The HTTP server would replace that data directly into theImageViewData
struct. We could try base64 decoding this data.The text was updated successfully, but these errors were encountered: