Opened 5 years ago

Last modified 3 years ago

#2629 assigned enhancement

Scheduler and ChangeSource Messages

Reported by: dustin Owned by:
Priority: major Milestone: 0.9.+
Version: Keywords: simple
Cc:

Description

Add messages to the scheduler and change source resource types, one for each possible change in status. This will allow users to track which master has a running scheduler, among other things.

Change History (5)

comment:1 Changed 5 years ago by tardyp

dustin: unless really needed, I would prefer to stick with the generic way of sending generic message with everything in it.

This is much simpler design, and we still have an optimization path if it is seen that this is a performance bottleneck (which I highly doubt:I dont expect to have a big difference sending messages with length < 1500 bytes, i.e. one packet)

comment:2 Changed 4 years ago by dustin

  • Owner set to dustin
  • Status changed from new to assigned

comment:3 Changed 4 years ago by dustin

  • Owner dustin deleted

comment:4 Changed 4 years ago by dustin

  • Summary changed from [nine] Scheduler and ChangeSource Messages to Scheduler and ChangeSource Messages

@tardyp: This is still the generic way -- it just means actually sending a message (containing the entire scheduler or changesource definition) on every state change.

comment:5 Changed 3 years ago by dustin

  • Milestone changed from 0.9.0 to 0.9.+
Note: See TracTickets for help on using tickets.