PATCH: 1st part of the patch to solve the "large file upload problem"

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 06 June 2003 13:45, you wrote:
> On Friday 06 June 2003 05:26, Waldo Bastian wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Friday 06 June 2003 06:07, Dawit A. wrote:
> > > Comments ? Feedback ?
> >
> > Is there a reason why the post job stores the file and not the http slave
> > itself? The same problem will need to be solved for HTTP PUT (for webdav
> > mostly) and it's not very feasable to do that in the job.
>
> I presume you are talking about the backwards compatability ctor that
> attempts to save the provided buffer from memory to disk.  It was not
> intented to be a storage in case the data was re-requested.  The intention
> was simply to avoid another duplication (copying) of the data. However, in
> hind sight assigning QByteArray's does shallow copying so there is no
> reason for it really.  I'll change it.

No, I mean you handle this whole resending of data in the job, I think the 
slave should take care of it.

Cheers,
Waldo
- -- 
bastian at kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+4H+dN4pvrENfboIRAg73AKCUsua3ng/Bed2wrMtHkxsvDb8eaQCfUnVA
k672l7MjId/QSqTTqytsxbM=
=BVM2
-----END PGP SIGNATURE-----