summaryrefslogtreecommitdiffstats
path: root/kdejava/koala/org/kde/koala/Scheduler.java
diff options
context:
space:
mode:
Diffstat (limited to 'kdejava/koala/org/kde/koala/Scheduler.java')
-rw-r--r--kdejava/koala/org/kde/koala/Scheduler.java34
1 files changed, 17 insertions, 17 deletions
diff --git a/kdejava/koala/org/kde/koala/Scheduler.java b/kdejava/koala/org/kde/koala/Scheduler.java
index 68094974..1493b2d0 100644
--- a/kdejava/koala/org/kde/koala/Scheduler.java
+++ b/kdejava/koala/org/kde/koala/Scheduler.java
@@ -11,17 +11,17 @@ import org.kde.qt.TQObject;
/**
- The KIO.Scheduler manages io-slaves for the application.
+ The TDEIO.Scheduler manages io-slaves for the application.
It also queues jobs and assigns the job to a slave when one
becomes available.
There are 3 possible ways for a job to get a slave:
<h3>1. Direct</h3>
This is the default. When you create a job the
- KIO.Scheduler will be notified and will find either an existing
+ TDEIO.Scheduler will be notified and will find either an existing
slave that is idle or it will create a new slave for the job.
Example:
<pre>
- TransferJob job = KIO.get(KURL("http://www.kde.org"));
+ TransferJob job = TDEIO.get(KURL("http://www.kde.org"));
</pre>
<h3>2. Scheduled</h3>
If you create a lot of jobs, you might want not want to have a
@@ -31,8 +31,8 @@ import org.kde.qt.TQObject;
a job from the queue.
Example:
<pre>
- TransferJob job = KIO.get(KURL("http://www.kde.org"));
- KIO.Scheduler.scheduleJob(job);
+ TransferJob job = TDEIO.get(KURL("http://www.kde.org"));
+ TDEIO.Scheduler.scheduleJob(job);
</pre>
<h3>3. Connection Oriented</h3>
For some operations it is important that multiple jobs use
@@ -44,28 +44,28 @@ import org.kde.qt.TQObject;
one after the other.
Example:
<pre>
- Slave slave = KIO.Scheduler.getConnectedSlave(
+ Slave slave = TDEIO.Scheduler.getConnectedSlave(
KURL("pop3://bastian:password@mail.kde.org"));
- TransferJob job1 = KIO.get(
+ TransferJob job1 = TDEIO.get(
KURL("pop3://bastian:password@mail.kde.org/msg1"));
- KIO.Scheduler.assignJobToSlave(slave, job1);
- TransferJob job2 = KIO.get(
+ TDEIO.Scheduler.assignJobToSlave(slave, job1);
+ TransferJob job2 = TDEIO.get(
KURL("pop3://bastian:password@mail.kde.org/msg2"));
- KIO.Scheduler.assignJobToSlave(slave, job2);
- TransferJob job3 = KIO.get(
+ TDEIO.Scheduler.assignJobToSlave(slave, job2);
+ TransferJob job3 = TDEIO.get(
KURL("pop3://bastian:password@mail.kde.org/msg3"));
- KIO.Scheduler.assignJobToSlave(slave, job3);
+ TDEIO.Scheduler.assignJobToSlave(slave, job3);
// ... Wait for jobs to finish...
- KIO.Scheduler.disconnectSlave(slave);
+ TDEIO.Scheduler.disconnectSlave(slave);
</pre>
Note that you need to explicitly disconnect the slave when the
connection goes down, so your error handler should contain:
<pre>
- if (error == KIO.ERR_CONNECTION_BROKEN)
- KIO.Scheduler.disconnectSlave(slave);
+ if (error == TDEIO.ERR_CONNECTION_BROKEN)
+ TDEIO.Scheduler.disconnectSlave(slave);
</pre>
See {@link SchedulerSignals} for signals emitted by Scheduler
- @short The KIO.Scheduler manages io-slaves for the application.
+ @short The TDEIO.Scheduler manages io-slaves for the application.
@see Slave
@see Job
@@ -155,7 +155,7 @@ public class Scheduler extends TQObject implements DCOPObjectInterface {
the that was started.
Register the mainwindow <code>wid</code> with the KIO subsystem
Do not call this, it is called automatically from
- void KIO.Job.setWindow(TQWidget).
+ void TDEIO.Job.setWindow(TQWidget).
@param wid the window to register
@short Send the slave that was put on hold back to TDELauncher.
*/