On Sat, 12 Apr 2014, Jeremy Ruston wrote:
As far as changing the content type for PUTs and GETs, I can flick the
switch for TW5 very easily, but I guess we might worry about backwards
compatibility - when the time comes would it be reasonable for me to sniff
the TiddlyWeb version number in /status to determine which content type to
use?
That's fair assuming status is being run on the server (it's a
plugin so though it is usually there, it doesn't _have_ to be).
I'm not super concerned with maintaining aggressive backwards
compatibility because I want people to aggressively upgrade as and
when they need.
With respect to using semantically meaningful content types for TW5's JSON
tiddlers, I've opened a ticket:
https://github.com/Jermolene/TiddlyWiki5/issues/551
I've created the pair on the tiddlyweb side:
https://github.com/tiddlyweb/tiddlyweb/issues/99
--
Chris Dent http://burningchrome.com/
[...]
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.
