Scheduled-task pattern: Difference between revisions

Revision as of 21:28, 3 January 2003

Latest revision as of 15:25, 14 May 2021

(15 intermediate revisions by 11 users not shown)

Line 1:

A '''scheduled-task pattern''' is a type of software [[design pattern]] used with real-time systems.<ref>{{Cite web|url=https://subscription.packtpub.com/book/application_development/9781785887130/5/ch05lvl1sec61/scheduled-task-pattern|title=Scheduled Task pattern|website=subscription.packtpub.com|language=en|access-date=2019-05-24}}</ref> It is not to be confused with the "[[scheduler pattern]]".

In software development, '''scheduled-task pattern''' is one of [[design pattern]]s.

While the [[scheduler pattern]] delays access to a resource (be it a function, variable, or otherwise) only as long as absolutely needed, the scheduled-task pattern delays execution until a determined time. This is important in real-time systems for a variety of reasons.

The '''scheduled task pattern''' is a [[design pattern]] used in [[software engineering]]. It is used to ensure that desired operations are performed at specific points in the future.

==References==

In [[Real-time]] [[Computer software|systems]], it is often necessary to ensure that something is done at a specific time. A scheduler object (note: not quite the same as [[scheduler pattern]]) keeps track of these actions, and invokes them at the appropriate times.

{{Reflist}}

== External Link links==

Times may be expressed as "wall time" or as some sort of internal time ("ticks", milliseconds-since-startup, etc.).

*{{Cite web|url=https://docs.microsoft.com/en-us/dotnet/standard/asynchronous-programming-patterns/task-based-asynchronous-pattern-tap|title=Task-based Asynchronous Pattern (TAP)|last=rpetrusha|website=docs.microsoft.com|language=en-us|access-date=2019-05-25}}

*{{Cite web|url=https://pubs.vmware.com/vsphere-51/index.jsp?topic=/com.vmware.vsphere.vcenterhost.doc/GUID-03B90638-6C70-4379-8CAF-D66866D115F4.html|title=Create a Scheduled Task in the vSphere Web Client |work=VMware vSphere 5.1 |access-date=2019-05-25}}

==See also==

If highly accurate scheduling of tasks is needed (to milliseconds or less), the scheduler task needs to run at a very high priority, or be hooked into a high-frequency interrupt routine.

*[[Command pattern]]

*[[Memento pattern]]

'''See also:''' [[Command pattern]], [[Memento pattern]]

[[Category:Software design patterns]]

== External Link ==

MartinFowler's ''Recurring Events'' document at PPR: http://c2.com/ppr/schedule.pdf

{{compu-stub}}