1 files changed, 6 insertions, 6 deletions

diff --git a/certmanager/storedtransferjob.h b/certmanager/storedtransferjob.h
index ddc687fc..7fab7706 100644
--- a/certmanager/storedtransferjob.h
+++ b/certmanager/storedtransferjob.h
@@ -23,28 +23,28 @@
 #include <kio/job.h>
 
 // To be moved to KIO?
-namespace KIOext {
+namespace TDEIOext {
 
 /**
  * StoredTransferJob is a TransferJob (for downloading or uploading data) that
  * also stores a TQByteArray with the data, making it simpler to use than the
  * standard TransferJob.
  *
- * For KIO::get it puts the data into the member TQByteArray, so the user
+ * For TDEIO::get it puts the data into the member TQByteArray, so the user
  * of this class can get hold of the whole data at once by calling data()
  * when the result signal is emitted.
  * You should only use StoredTransferJob to download data if you cannot
  * process the data by chunks while it's being downloaded, since storing
  * everything in a TQByteArray can potentially require a lot of memory.
  *
- * For KIO::put the user of this class simply provides the bytearray from
+ * For TDEIO::put the user of this class simply provides the bytearray from
  * the start, and the job takes care of uploading it.
  * You should only use StoredTransferJob to upload data if you cannot
  * provide the in chunks while it's being uploaded, since storing
  * everything in a TQByteArray can potentially require a lot of memory.
  *
  */
-class StoredTransferJob : public KIO::TransferJob {
+class StoredTransferJob : public TDEIO::TransferJob {
     Q_OBJECT
   
 
@@ -76,8 +76,8 @@ public:
     TQByteArray data() const { return m_data; }
 
 private slots:
-    void slotData( KIO::Job *job, const TQByteArray &data );
-    void slotDataReq( KIO::Job *job, TQByteArray &data );
+    void slotData( TDEIO::Job *job, const TQByteArray &data );
+    void slotDataReq( TDEIO::Job *job, TQByteArray &data );
 private:
     TQByteArray m_data;
     int m_uploadOffset;