Session Maps are currently computed on the device when they get loaded.
That creates some DREADFUL lag when they first load up.
We can reduce lag by lowering resolution, but that creates meh results.
So, the solution is probably to cache it serverside and just serve it.
Alternatively and maybe more efficient since we want to retain the ability to preview a Session Map, we basically take the map generated client-side during edit and push it to the server when we update. Then just load it. Basically we treat it as an image that the client (generates and) uploads.
Session Maps are currently computed on the device when they get loaded.
That creates some DREADFUL lag when they first load up.
We can reduce lag by lowering resolution, but that creates meh results. So, the solution is probably to cache it serverside and just serve it.
Alternatively and maybe more efficient since we want to retain the ability to preview a Session Map, we basically take the map generated client-side during edit and push it to the server when we update. Then just load it. Basically we treat it as an image that the client (generates and) uploads.