Oleg,
Sorry for my slow reply, but I wanted to report that this solution worked
well in case it helps others in the future. Thank you for taking the time
to help!
Joe
On Thu, Dec 18, 2014 at 12:12 PM, Joe Barnes barne...@gmail.com wrote:
Oh wow... I had not noticed that method on URL. I'll
On Wed, 2014-12-17 at 17:37 -0600, Joe Barnes wrote:
Hello community!
My team is faced with a problem where we need to send a resource that is
available via URL (more precisely, it is on our classpath). We are running
in a servlet container, so we don't have direct access to the file
Thanks for the insight, Oleg. I was not aware that the key to
repeatability was knowing the length in advance. That seems to suggest we
could have an API that accepted the stream and a length to produce a
repeatable multipart entity.
As for converting the URLs to files, I'm not sure there is a
On Thu, 2014-12-18 at 09:23 -0600, Joe Barnes wrote:
Thanks for the insight, Oleg. I was not aware that the key to
repeatability was knowing the length in advance. That seems to suggest we
could have an API that accepted the stream and a length to produce a
repeatable multipart entity.
As
Oh wow... I had not noticed that method on URL. I'll certainly give it a
try. Thanks!
Joe
On Thu, Dec 18, 2014 at 10:06 AM, Oleg Kalnichevski ol...@apache.org
wrote:
On Thu, 2014-12-18 at 09:23 -0600, Joe Barnes wrote:
Thanks for the insight, Oleg. I was not aware that the key to
Hello community!
My team is faced with a problem where we need to send a resource that is
available via URL (more precisely, it is on our classpath). We are running
in a servlet container, so we don't have direct access to the file system.
I completely understand why the chunks are marked as
