Anonymous user
Talk:Base64 encode data: Difference between revisions
→task requirements: Renaming is a good idea
(→task requirements: Concur with “HTTP not required in task”) |
(→task requirements: Renaming is a good idea) |
||
Line 89:
::::: Don't make downloading the file a requirement of the task itself; it's just a source of binary data, not an HTTP client task (we've got another task for that). But it is reasonable to have a defined input to work with so that outputs can be compared. (Note that whitespace differences in the output are going to have to be allowable; the base64 spec ''specifically'' allows them.) –[[User:Dkf|Donal Fellows]] ([[User talk:Dkf|talk]]) 10:31, 29 August 2013 (UTC)
:: There's not much logical difference between a string and an image at this level; you're really encoding a byte sequence (and logically you have to start by encoding both the string and the image as bytes before you can apply the encoding at all, even if that's typically trivial for ASCII strings). I'll rename the task though, probably to “Base64 encoding” so as to better reflect what the task actually asks for. I encourage writing a matching decoding task; we can put in cross links between the two too. –[[User:Dkf|Donal Fellows]] ([[User talk:Dkf|talk]]) 10:36, 29 August 2013 (UTC)
| |||