Saving condition images
Dealing with images is a complicated set of circumstances.
First, if I'm going to keep track of all my different condition pictures, it can overwhelm my web hosting server pretty quickly.
Just me, no problem, but, add a few people to the mix and it starts taking significant amounts of room.
To deal with all those images, i needed to pull out my deep thinking cap. So here is the way I'll do it.
There is a way for me to store information on a user's machine. It's called indexedDB. The problem is this, it has to be extremely secure, so the way an internet browser deals with it, is that it saves information locally but is only accessible from that browser and that website.
Different browser, different data repository. So... how to deal with such diversity, especially considering that the user has multiple machines. The only way I can see them being able to access thir images is to use deep Synchronization techniques.
So, first, if they are on their smartphones, then let them know it is being saved on their smartphone and the images can only be seen from their smartphone. If they use their desktop computer then they need to initiate a Synchronization of their smartphone and their desktop images. That has to be done easily.
If I see that they have synchronized at any time in the past, I can temporarily store a certain amount of images on my server and automatically synchronize when they open the other machine. It's messy and I have to come up with ways to make it as transparent to the user as possible. That way, if they keep switching machines, like I do, the images will always be available for comparison.
That's a tall order.
Pierre
Comments
Post a Comment