On Feb 26, 3:05 pm, Jeppe Nejsum Madsen wrote:
> On Fri, Feb 26, 2010 at 1:53 PM, Marius wrote:
>
> > On Feb 26, 1:29 pm, Jeppe Nejsum Madsen wrote:
> >> On Fri, Feb 26, 2010 at 12:06 PM, Jeppe Nejsum Madsen
> >> wrote:
>
> >> > So the thread creation/scheduling and the two times file copyin
On Fri, Feb 26, 2010 at 1:53 PM, Marius wrote:
>
>
> On Feb 26, 1:29 pm, Jeppe Nejsum Madsen wrote:
>> On Fri, Feb 26, 2010 at 12:06 PM, Jeppe Nejsum Madsen
>> wrote:
>>
>> > So the thread creation/scheduling and the two times file copying could be
>> > avoided by writing directly to the output
On Feb 26, 1:29 pm, Jeppe Nejsum Madsen wrote:
> On Fri, Feb 26, 2010 at 12:06 PM, Jeppe Nejsum Madsen
> wrote:
>
> > So the thread creation/scheduling and the two times file copying could be
> > avoided by writing directly to the output stream. But I agree this would
> > have to be special ca
On Fri, Feb 26, 2010 at 12:06 PM, Jeppe Nejsum Madsen wrote:
> So the thread creation/scheduling and the two times file copying could be
> avoided by writing directly to the output stream. But I agree this would
> have to be special cased somehow. It's not an urgent issue atm, but I'll
> try to s
Marius writes:
> On Feb 26, 11:50 am, Jeppe Nejsum Madsen wrote:
>> Hi,
>>
>> I need to create a response that downloads a file. The file is
>> generated by a 3rd party api that takes an output stream as the target
>> for the file. As the file can be rather large, I would like to stream
>> this
On Feb 26, 11:50 am, Jeppe Nejsum Madsen wrote:
> Hi,
>
> I need to create a response that downloads a file. The file is
> generated by a 3rd party api that takes an output stream as the target
> for the file. As the file can be rather large, I would like to stream
> this file directly to the cl
