.TH "KIO::StoredTransferJob" kde3 "11 Jun 2005" "Version Version 3.4.1" "kio Library" \" -*- nroff -*-
.ad l
.nh
.SH NAME
KIO::StoredTransferJob \- \fBStoredTransferJob\fP is a \fBTransferJob\fP (for downloading or uploading data) that also stores a \fBQByteArray\fP with the data, making it simpler to use than the standard \fBTransferJob\fP.  

.PP
.SH SYNOPSIS
.br
.PP
\fC#include <jobclasses.h>\fP
.PP
Inherits \fBKIO::TransferJob\fP.
.PP
.SS "Public Member Functions"

.in +1c
.ti -1c
.RI "\fBStoredTransferJob\fP (const \fBKURL\fP &url, int command, const \fBQByteArray\fP &packedArgs, const \fBQByteArray\fP &_staticData, bool showProgressInfo)"
.br
.ti -1c
.RI "void \fBsetData\fP (const \fBQByteArray\fP &arr)"
.br
.ti -1c
.RI "\fBQByteArray\fP \fBdata\fP () const "
.br
.in -1c
.SH "Detailed Description"
.PP 
\fBStoredTransferJob\fP is a \fBTransferJob\fP (for downloading or uploading data) that also stores a \fBQByteArray\fP with the data, making it simpler to use than the standard \fBTransferJob\fP. 

For \fBKIO::storedGet\fP it puts the data into the member \fBQByteArray\fP, so the user of this class can get hold of the whole data at once by calling \fBdata()\fP when the result signal is emitted. You should only use \fBStoredTransferJob\fP to download data if you cannot process the data by chunks while it's being downloaded, since storing everything in a \fBQByteArray\fP can potentially require a lot of memory.
.PP
For \fBKIO::storedPut\fP the user of this class simply provides the bytearray from the start, and the job takes care of uploading it. You should only use \fBStoredTransferJob\fP to upload data if you cannot provide the in chunks while it's being uploaded, since storing everything in a \fBQByteArray\fP can potentially require a lot of memory.
.PP
\fBSince:\fP
.RS 4
3.3 
.RE
.PP

.PP
Definition at line 1034 of file jobclasses.h.
.SH "Constructor & Destructor Documentation"
.PP 
.SS "StoredTransferJob::StoredTransferJob (const \fBKURL\fP & url, int command, const \fBQByteArray\fP & packedArgs, const \fBQByteArray\fP & _staticData, bool showProgressInfo)"
.PP
Do not create a \fBStoredTransferJob\fP. 
.PP
Use \fBstoredGet()\fP or \fBstoredPut()\fP instead. 
.PP
\fBParameters:\fP
.RS 4
\fIurl\fP the url to get or put 
.br
\fIcommand\fP the command to issue 
.br
\fIpackedArgs\fP the arguments 
.br
\fI_staticData\fP additional data to transmit (e.g. in a HTTP Post) 
.br
\fIshowProgressInfo\fP true to show progress information to the user
.RE
.PP

.PP
Definition at line 1331 of file job.cpp.
.PP
References QObject::connect(), data(), and KIO::TransferJob::dataReq().
.SH "Member Function Documentation"
.PP 
.SS "void StoredTransferJob::setData (const \fBQByteArray\fP & arr)"
.PP
Set data to be uploaded. 
.PP
This is for put jobs. Automatically called by \fBKIO::storedPut\fP(const \fBQByteArray\fP &, ...), do not call this yourself. 
.PP
Definition at line 1344 of file job.cpp.
.PP
Referenced by KIO::storedPut().
.SS "\fBQByteArray\fP KIO::StoredTransferJob::data () const\fC [inline]\fP"
.PP
Get hold of the downloaded data. 
.PP
This is for get jobs. You're supposed to call this only from the slot connected to the \fBresult()\fP signal. 
.PP
Definition at line 1063 of file jobclasses.h.
.PP
Referenced by StoredTransferJob().

.SH "Author"
.PP 
Generated automatically by Doxygen for kio Library from the source code.
