Ability to assign priorities to async continuations complemented by plugabble job aquisition strategies

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Won't Fix
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: engine
    • None

      In a shared engine deployment, process tasks may have differing timeliness NFR's. Hence I'd like the ability to assign priorities to tasks such that the job executor job acquisition strategy leverages these priorities.

      Additional Considerations:
      Perhaps timers should have highest priority such that they are always executed first.
      A pluggable job aquisition strategy is desirable such that I can select an appropriate strategy.
      Sample strategies include - select based on priority order, select on priority*(Systime() - DueDate)

            Assignee:
            Unassigned
            Reporter:
            Rob Parker
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: