-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
On 10/12/2010 5:15 PM, Brian Pontarelli wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
On 10/4/2010 11:43 AM, Brian Pontarelli wrote:
I figured that the original File and the File written out by the
FileUpload would have
At first I thought the lengths were different, but that was actually in a much
more complex set of tests. I wrote the test code below after my first post to
the list.
Here's what that code is doing:
The lengths are the same, but the byte at position 305 is -1 rather than -66.
The answers to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
On 10/4/2010 11:43 AM, Brian Pontarelli wrote:
I figured that the original File and the File written out by the
FileUpload would have different bytes at the start or end and it was
my mock input stream that was causing the issue. To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
On 10/5/2010 12:49 PM, Brian Pontarelli wrote:
I haven't tried additional files yet, mostly because it should work
for any file in the universe.
Of course. I'm not trying to verify that there is a problem (there's
clearly a problem
I'm using the FileUpload library and running into a very odd issue that I can't
seem to track down. I stepped through some of the FileUpload code and had to
abandon that for a while as it looked like it would take a considerable amount
of time to figure it out that way.
Here's what I'm doing.
