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 snapshot.txt returns the result for only viewer key (the one specified as the get parameter), but I think we should have some possibility of sending a snapshot for all viewer keys in the exposedModel in one transaction, so one could open a new endpoint "snapshots.txt" which returns JSON-delimited basd64-encoded screenshots for each viewer, basically like this:
When we switch over to binary transfer for images again, this could easily be solved by returning one huge image that is shared between the different parts (or use more advanced techniques).
The text was updated successfully, but these errors were encountered:
For the Apache module this should be quite straightforward. But wasn't base64-decoding surprisingly slow? Not that I have a brilliant scheme at hand that can send multiple images in one go.
Currently snapshot.txt returns the result for only viewer key (the one specified as the get parameter), but I think we should have some possibility of sending a snapshot for all viewer keys in the exposedModel in one transaction, so one could open a new endpoint "snapshots.txt" which returns JSON-delimited basd64-encoded screenshots for each viewer, basically like this:
This should also be seen in conjunction with the auto-proxy branch, so perhaps the format should be:
When we switch over to binary transfer for images again, this could easily be solved by returning one huge image that is shared between the different parts (or use more advanced techniques).
The text was updated successfully, but these errors were encountered: