> Note that `text/x-tiddler` on PUT would make sense if the HTTP
> Content-Type header didn't end up as the respective tiddler's `type`
> attribute - but that's a different, probably unhelpful discussion.
Correction (my tests last nights were misleading): The representation's
`type` actually takes precedence over the Content-Type header.
$ echo '{ "type": "application/json" }' | \
curl -X PUT -H "Content-Type: text/x-tiddler" --data-binary @- \
http://example.org/.../foo
The resulting tiddler has `type: application/json`.
However, while semantically that seems more correct ("here's a tiddler",
rather than some arbitary JSON), I'm not sure the distinction matters on
PUT. On GET it matters because it actually changes the representation.
> Wind tunnel?!? Sounds like that could be helpful for my occasional
> mental befuddlement.
https://www.indoor-skydiving.com (went there to practice for my upcoming
license completion) - can definitely recommend it.
--
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.
