Scheduler pattern: Difference between revisions

Content deleted Content added

Revision as of 21:31, 3 January 2003 edit TakuyaMurata (talk \| contribs) Extended confirmed users, IP block exemptions, Pending changes reviewers 92,676 edits No edit summary ← Previous edit		Latest revision as of 19:34, 2 December 2015 edit undo Qwertyus (talk \| contribs) Extended confirmed users 31,640 edits redirecting to Scheduling (computing), which covers the same topic; the only source I can find for scheduling as a design pattern is the self-published http://www.c2.com/cgi/wiki?SchedulerPattern, which treats everything as a pattern
(20 intermediate revisions by 16 users not shown)
Line 1: #REDIRECT [[Scheduling (computing)]] ~~In software development, '''Scheduler pattern''' is one of [[design pattern]]s.~~ ~~When there are concurrent requests for a resource, it is necessary to synchronize access.~~ ~~'''Therefore,'''~~ ~~Implement a ''scheduler'' that selects which request will be allowed to execute next.~~ ~~Scheduling policies may be first-come/first-served, priority-based, or otherwise.~~ ~~Using the StrategyPattern, one can customize the behavior of the scheduler for particular configurations or applications.~~ ~~Consider the CommandPattern for representation of queued requests.~~ ~~'''Other Related Patterns:''' LockPattern, ReadWriteLock, MediatorPattern, InterruptibleCommand, ReactorPattern~~ ~~----~~ ~~CategoryPattern \| CategoryConcurrencyPatterns~~