Call it statusEvent and send messages to it when interesting things happen. The message should contain all of the data relevant to the event. The first field should identify what the event is about.
Took a slightly different approach, treating events as a dataflow within the Health activity. Defined a publishEvent() routine, and am now sending out a test event just before the spreadsheet titles are sent. There's some implied enhancement work by the comments around publishEvent. Need to move the field definitions closer to the beginning of the source file - they're too easy to find .
Call it statusEvent and send messages to it when interesting things happen. The message should contain all of the data relevant to the event. The first field should identify what the event is about.
Took a slightly different approach, treating events as a dataflow within the Health activity. Defined a publishEvent() routine, and am now sending out a test event just before the spreadsheet titles are sent. There's some implied enhancement work by the comments around publishEvent. Need to move the field definitions closer to the beginning of the source file - they're too easy to find.