original: Design philosophies Two basic designs exist: Event-driven (priority scheduling) designs switch tasks only when an event of higher priority needs service, called pre-emptive priority.
simplifications: Two basic designs exist: Event-driven designs switch tasks only when an event of higher priority needs service, called pre-emptive priority. Two basic designs exist: Event-driven (priority scheduling) designs switch tasks only when an event of higher priority needs service. It is called pre-emptive priority. Two designs exist: Event-driven designs switch tasks only when higher priority events need service called pre-emptive priority. Two basic designs exist. One is event driven designs. The other is priority design or priority scheduling. At times, an event-driven design can be a priority design. This occurs when the design needs a higher level of service. Design philosophies: Two basic designs exist: Event-driven (priority scheduling) designs switch tasks only when a higher priority event needs service. This is called pre-emptive priority. There are two basic designs. The Event-driven (priority scheduling) designs switch tasks only when an event of higher importance needs service. That is called pre-emptive priority. Event-driven designs switch tasks only when a more important event needs service. Event-driven (priority scheduling) designs switch tasks only when pre-emptive priority(higher priority) needs service called. Event-driven designs switch tasks only when an event of higher priority needs service. Event-driven (priority scheduling) designs switch tasks only when an event of higher priority needs service, called pre-emptive priority, is a type of design philosophy