| commit | f29701aeccfc59f521f13b5e2ee73ff15fc99147 | |
| author | Eric Wong <normalperson@yhbt.net> | |
| Fri, 17 Apr 2009 05:53:54 +0000 (16 22:53 -0700) | ||
| committer | Eric Wong <normalperson@yhbt.net> | |
| Fri, 17 Apr 2009 05:57:12 +0000 (16 22:57 -0700) | ||
| tree | c96187a363e66aa330a9829d210204912860af7f | treesnapshot (tar.gz zip) |
| parent | f2e90a9f15efda1abc87cde00bb341fdf3368985 | commitdiff |
test_upload: ensure StringIO objects are binary
Sockets always return binary encoded data, so when
StringIO.new(string) is called, that StringIO object inherits
the encoding of the initial string it was created with.
And yes, Ruby 1.9 still makes me seriously uncomfortable with
I/O manipulation since the encoding layer does things behind my
back. UNIX is (and should always be) just a bag of bytes!
Signed-off-by: Eric Wong <normalperson@yhbt.net>
Sockets always return binary encoded data, so when
StringIO.new(string) is called, that StringIO object inherits
the encoding of the initial string it was created with.
And yes, Ruby 1.9 still makes me seriously uncomfortable with
I/O manipulation since the encoding layer does things behind my
back. UNIX is (and should always be) just a bag of bytes!
Signed-off-by: Eric Wong <normalperson@yhbt.net>
| test/unit/test_upload.rb | diffblobblamehistory |