register a contentType for Waterbear

[dethe]

We need this for proper upload/downloads.

[nikhilNathwani]

I'm not sure I'm following, could you clarify what this means? Are you saying we need a catch-all type for any sort of upload/download?

[dethe]

This is a reminder that Waterbear files should have their own contentType (or content-type) registered with the IETF. When you send files around through email or HTTP, the content-type is is what tells the browser or other client how to process that file. For example a file with a content-type of 'image/jpeg' will be viewed as an image in a browser, but could also be opened with an image editing program when downloaded. Web pages themselves have content-type 'text/html'. Rather than waterbear save files simply being JSON, it would be better to have our own file extension and content-type, even if they remain JSON internally, because you can't simply open any JSON file in Waterbear. So instead of mySaveFile.json with type 'application/json' we could have mySaveFile.tardigrade (or whatever, but .wb has been taken: http://filext.com/file-extension/WB ) of type 'application/waterbear'.

[nikhilNathwani]

Ohh ok got it, thanks Dethe