Right now, image hashes are unique and therefore you're currently unable to update an image, but keep the same URL. This defeats a lot of benefits from having DaaS ( Diagrams as a service) because then you have to update 2 areas of code instead of one.
Proposition:
Realistically need to have authentication to do this correctly. For simplicity I think it would work to give the user capability to add their own client id, their own image name and then we can hash serverside with 3 tokens.
The downside is that collisions can still occur, which could theoretically cause some really odd behavior..
Potential solution to remediate collisions (prior to integrating auth) is to add a client id generate to get a more random hash.
All in all, without auth, the UX becomes poor. Something worth iterating on.
Right now, image hashes are unique and therefore you're currently unable to update an image, but keep the same URL. This defeats a lot of benefits from having DaaS ( Diagrams as a service) because then you have to update 2 areas of code instead of one.
Proposition:
Realistically need to have authentication to do this correctly. For simplicity I think it would work to give the user capability to add their own client id, their own image name and then we can hash serverside with 3 tokens.
The downside is that collisions can still occur, which could theoretically cause some really odd behavior..
Potential solution to remediate collisions (prior to integrating auth) is to add a client id generate to get a more random hash.
All in all, without auth, the UX becomes poor. Something worth iterating on.