> So, it sounds like the only change on the TW5 side would be to change > the content type for PUTs
Well, actually... I've had some scenic train time to think about this today, or perhaps it was the wind tunnel clearing my pathways - either way, I've come to the conclusion that a tiddler's `type` refers exclusively to that tiddler's `text`. Thus PUTing a tiddler with `type: text/x-tiddler` is not only redundant, it also eliminates the standard mechanism for describing the content type of the tiddler body. IOW, it's a hack. In short: If the body is $contentType, then `type` should say so. Where `text/x-tiddler` (or whatever) makes perfect sense is on GET, as that's where the client states what it expects to receive - and clearly in the case of tiddler editors, that's a tiddler rather than "some JSON". (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.) cdent: I realize this contradicts yesterday's conclusion, but I'd warned you that my brain wasn't reliable then (not that it ever is). Not that we didn't discuss those aspects, but it wasn't quite phrased in these terms. -- 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.
