Update of /cvsroot/webware/Webware/TaskKit/Docs
In directory sc8-pr-cvs1:/tmp/cvs-serv18133
Modified Files:
QuickStart.html
Log Message:
Fixed typos per patch [ 684583 ] Fix typos in Quickstart guide
Index: QuickStart.html
===================================================================
RCS file: /cvsroot/webware/Webware/TaskKit/Docs/QuickStart.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** QuickStart.html 10 Jun 2002 02:07:58 -0000 1.4
--- QuickStart.html 14 Feb 2003 10:23:02 -0000 1.5
***************
*** 23,27 ****
System administrators for example know very well how to start new <code>cron</code> jobs or the
corresponding Windows analogues. So, why does a web application server like Webware/WebKit
! need it's own scheduling framework. The answer is simple: Because it knows better how to
react to a failed job, has access to internal data structures, which otherwise would have
to be exposed to the outside world and last but not least it needs scheduling capabilities
--- 23,27 ----
System administrators for example know very well how to start new <code>cron</code> jobs or the
corresponding Windows analogues. So, why does a web application server like Webware/WebKit
! need its own scheduling framework. The answer is simple: Because it knows better how to
react to a failed job, has access to internal data structures, which otherwise would have
to be exposed to the outside world and last but not least it needs scheduling capabilities
***************
*** 33,37 ****
problem is already solved (remember the Python slogan: batteries included), but strange
enough there has not much work been done in this area. The two standard Python modules
! <code>sched.py</code> and <code>bisect.py</code> are way to simple, not really object oriented
and also not multithreaded. This was the reason to develop a new scheduling framework, which
can not only be used with Webware but also with general purpose Python programs. Unfortunately
--- 33,37 ----
problem is already solved (remember the Python slogan: batteries included), but strange
enough there has not much work been done in this area. The two standard Python modules
! <code>sched.py</code> and <code>bisect.py</code> are way too simple, not really object oriented
and also not multithreaded. This was the reason to develop a new scheduling framework, which
can not only be used with Webware but also with general purpose Python programs. Unfortunately
***************
*** 48,52 ****
be able to use web wrappers (for Zope, Webware, Quixote,..) around clearly designed Python
classes and not be forced to use one framework. Time will tell if this is just a dream
! or if people will reinvent the "python weels" over and over again.
<h2>Tasks</h2>
--- 48,52 ----
be able to use web wrappers (for Zope, Webware, Quixote,..) around clearly designed Python
classes and not be forced to use one framework. Time will tell if this is just a dream
! or if people will reinvent the "python wheels" over and over again.
<h2>Tasks</h2>
***************
*** 55,59 ****
The TaskKit implements the three classes <code>Scheduler, TaskHandler</code> and <code>Task</code>.
Let's begin with the simplest one, i.e. Task. It's an abstract base class, from which you
! have to derive you own task classes by overriding the <code>run()</code>-method like in
the following example:
--- 55,59 ----
The TaskKit implements the three classes <code>Scheduler, TaskHandler</code> and <code>Task</code>.
Let's begin with the simplest one, i.e. Task. It's an abstract base class, from which you
! have to derive your own task classes by overriding the <code>run()</code>-method like in
the following example:
***************
*** 98,102 ****
It's generally better to let the task finish and use the <code>unregister()</code> and
<code>disable()</code> methods. The first really deletes the task after termination while
! the second only disables it's rescheduling. You can still use it afterwards. Right now the implementation
of <code>proceed()</code>
--- 98,102 ----
It's generally better to let the task finish and use the <code>unregister()</code> and
<code>disable()</code> methods. The first really deletes the task after termination while
! the second only disables its rescheduling. You can still use it afterwards. Right now the implementation
of <code>proceed()</code>
***************
*** 133,137 ****
the content will not be completely accurate (e.g. the number of comments will certainly
increase), but nobody really cares about that. The benefit is a dramatic reduction of
! database requests. For other pages (like older news with comments attached) it gives
more sense to generate static versions on demand. This is the case when the discussion
has come to an end, but somebody adds a comment afterwards and implicitely changes the
--- 133,137 ----
the content will not be completely accurate (e.g. the number of comments will certainly
increase), but nobody really cares about that. The benefit is a dramatic reduction of
! database requests. For other pages (like older news with comments attached) it makes
more sense to generate static versions on demand. This is the case when the discussion
has come to an end, but somebody adds a comment afterwards and implicitely changes the
***************
*** 144,148 ****
Let's look a litle bit closer at the static generation technique now. First of all we
need a <code>PageGenerator</code> class. To keep the example simple we just
! write the actual date into a file. In real live you will assemble much more complex data
into such static pages.
--- 144,148 ----
Let's look a litle bit closer at the static generation technique now. First of all we
need a <code>PageGenerator</code> class. To keep the example simple we just
! write the actual date into a file. In real life you will assemble much more complex data
into such static pages.
***************
*** 244,248 ****
<P>
When you click on the <code>Generate</code> button a new periodic <code>PageGenerator</code> task
! will be add to the Webware scheduler. Remember that this will generate a static page <code>static.html</code>
every 60 seconds (if you use the default values). The new task name is <code>"PageGenerator for filename"</code>,
so you can use this servlet to change the settings of already scheduled tasks (by rescheduling) or
--- 244,248 ----
<P>
When you click on the <code>Generate</code> button a new periodic <code>PageGenerator</code> task
! will be added to the Webware scheduler. Remember that this will generate a static page <code>static.html</code>
every 60 seconds (if you use the default values). The new task name is <code>"PageGenerator for filename"</code>,
so you can use this servlet to change the settings of already scheduled tasks (by rescheduling) or
***************
*** 257,261 ****
<code>_action_</code> construct which is very well explained in the Webware documentation though (just
in case you forgot that). <code>app.taskManager()</code> gives you the WebKit scheduler, which can be
! used to add new tasks. In real live you will have to make the scheduling information persistent
and reschedule all tasks after a WebKit restart because it would be quite annoying to enter this
data again and again. <code>PersistantScheduler</code> is a class which is on the ToDo list for the
--- 257,261 ----
<code>_action_</code> construct which is very well explained in the Webware documentation though (just
in case you forgot that). <code>app.taskManager()</code> gives you the WebKit scheduler, which can be
! used to add new tasks. In real life you will have to make the scheduling information persistent
and reschedule all tasks after a WebKit restart because it would be quite annoying to enter this
data again and again. <code>PersistantScheduler</code> is a class which is on the ToDo list for the
|