2 ms·
Great for complex apps in the browser and sharing complex save states! Bad for ordinary, mundane web applications and sharable URLs! Like, great for a musical
by moritzwarhier 4y ago
Great for complex apps in the browser and sharing complex save states!
Bad for ordinary, mundane web applications and sharable URLs!
Like, great for a musical step sequencer in the browser, bad for a website or HTTP service
OTOH, app state on websites of commercial service prodivders might be best represented by a JSON blob anyway.
In something like a checkout process or form submit, of course this doesn't matter much.
But I prefer human-readable URLs wherever possible.
And I implemented a similar pattern once, too.
It's a very interesting approach in intself.
Relevant POJO state tends to be small enough but long lists or resourcrs in a URL are not supported by most servers and not advisable.