\section{KIO::Stored\-Transfer\-Job Class Reference}
\label{classKIO_1_1StoredTransferJob}\index{KIO::StoredTransferJob@{KIO::StoredTransferJob}}
{\bf Stored\-Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1StoredTransferJob})} is a {\bf Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1TransferJob})} (for downloading or uploading data) that also stores a {\bf QByte\-Array} with the data, making it simpler to use than the standard {\bf Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1TransferJob})}.  


{\tt \#include $<$jobclasses.h$>$}

Inheritance diagram for KIO::Stored\-Transfer\-Job:\begin{figure}[H]
\begin{center}
\leavevmode
\includegraphics[width=79pt]{classKIO_1_1StoredTransferJob__inherit__graph}
\end{center}
\end{figure}
Collaboration diagram for KIO::Stored\-Transfer\-Job:\begin{figure}[H]
\begin{center}
\leavevmode
\includegraphics[width=294pt]{classKIO_1_1StoredTransferJob__coll__graph}
\end{center}
\end{figure}
\subsection*{Public Member Functions}
\begin{CompactItemize}
\item 
{\bf Stored\-Transfer\-Job} (const {\bf KURL} \&url, int command, const {\bf QByte\-Array} \&packed\-Args, const {\bf QByte\-Array} \&\_\-static\-Data, bool show\-Progress\-Info)
\item 
void {\bf set\-Data} (const {\bf QByte\-Array} \&arr)
\item 
{\bf QByte\-Array} {\bf data} () const 
\end{CompactItemize}


\subsection{Detailed Description}
{\bf Stored\-Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1StoredTransferJob})} is a {\bf Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1TransferJob})} (for downloading or uploading data) that also stores a {\bf QByte\-Array} with the data, making it simpler to use than the standard {\bf Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1TransferJob})}. 

For {\bf KIO::stored\-Get}{\rm (p.\,\pageref{namespaceKIO_a220})} it puts the data into the member {\bf QByte\-Array}, so the user of this class can get hold of the whole data at once by calling {\bf data()}{\rm (p.\,\pageref{classKIO_1_1StoredTransferJob_a2})} when the result signal is emitted. You should only use {\bf Stored\-Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1StoredTransferJob})} to download data if you cannot process the data by chunks while it's being downloaded, since storing everything in a {\bf QByte\-Array} can potentially require a lot of memory.

For {\bf KIO::stored\-Put}{\rm (p.\,\pageref{namespaceKIO_a221})} the user of this class simply provides the bytearray from the start, and the job takes care of uploading it. You should only use {\bf Stored\-Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1StoredTransferJob})} to upload data if you cannot provide the in chunks while it's being uploaded, since storing everything in a {\bf QByte\-Array} can potentially require a lot of memory.

\begin{Desc}
\item[Since:]3.3 \end{Desc}




Definition at line 1034 of file jobclasses.h.

\subsection{Constructor \& Destructor Documentation}
\index{KIO::StoredTransferJob@{KIO::Stored\-Transfer\-Job}!StoredTransferJob@{StoredTransferJob}}
\index{StoredTransferJob@{StoredTransferJob}!KIO::StoredTransferJob@{KIO::Stored\-Transfer\-Job}}
\subsubsection{\setlength{\rightskip}{0pt plus 5cm}Stored\-Transfer\-Job::Stored\-Transfer\-Job (const {\bf KURL} \& {\em url}, int {\em command}, const {\bf QByte\-Array} \& {\em packed\-Args}, const {\bf QByte\-Array} \& {\em \_\-static\-Data}, bool {\em show\-Progress\-Info})}\label{classKIO_1_1StoredTransferJob_a0}


Do not create a {\bf Stored\-Transfer\-Job}{\rm (p.\,\pageref{classKIO_1_1StoredTransferJob})}. 

Use {\bf stored\-Get()}{\rm (p.\,\pageref{namespaceKIO_a220})} or {\bf stored\-Put()}{\rm (p.\,\pageref{namespaceKIO_a221})} instead. \begin{Desc}
\item[Parameters:]
\begin{description}
\item[{\em url}]the url to get or put \item[{\em command}]the command to issue \item[{\em packed\-Args}]the arguments \item[{\em \_\-static\-Data}]additional data to transmit (e.g. in a HTTP Post) \item[{\em show\-Progress\-Info}]true to show progress information to the user\end{description}
\end{Desc}


Definition at line 1331 of file job.cpp.

References QObject::connect(), data(), and KIO::Transfer\-Job::data\-Req().

\subsection{Member Function Documentation}
\index{KIO::StoredTransferJob@{KIO::Stored\-Transfer\-Job}!setData@{setData}}
\index{setData@{setData}!KIO::StoredTransferJob@{KIO::Stored\-Transfer\-Job}}
\subsubsection{\setlength{\rightskip}{0pt plus 5cm}void Stored\-Transfer\-Job::set\-Data (const {\bf QByte\-Array} \& {\em arr})}\label{classKIO_1_1StoredTransferJob_a1}


Set data to be uploaded. 

This is for put jobs. Automatically called by {\bf KIO::stored\-Put}{\rm (p.\,\pageref{namespaceKIO_a221})}(const {\bf QByte\-Array} \&, ...), do not call this yourself. 

Definition at line 1344 of file job.cpp.

Referenced by KIO::stored\-Put().\index{KIO::StoredTransferJob@{KIO::Stored\-Transfer\-Job}!data@{data}}
\index{data@{data}!KIO::StoredTransferJob@{KIO::Stored\-Transfer\-Job}}
\subsubsection{\setlength{\rightskip}{0pt plus 5cm}{\bf QByte\-Array} KIO::Stored\-Transfer\-Job::data () const\hspace{0.3cm}{\tt  [inline]}}\label{classKIO_1_1StoredTransferJob_a2}


Get hold of the downloaded data. 

This is for get jobs. You're supposed to call this only from the slot connected to the {\bf result()}{\rm (p.\,\pageref{classKIO_1_1Job_l0})} signal. 

Definition at line 1063 of file jobclasses.h.

Referenced by Stored\-Transfer\-Job().

The documentation for this class was generated from the following files:\begin{CompactItemize}
\item 
jobclasses.h\item 
job.cpp\end{CompactItemize}
