semantics of periodics need to be nailed

bloom-lang / bud

Prototype Bud runtime (Bloom Under Development)

http://bloom-lang.net

Other

854 stars 60 forks source link

semantics of periodics need to be nailed #202

Closed jhellerstein closed 12 years ago

jhellerstein commented 13 years ago

shall we guarantee <2 items per periodic per timestep?
document that wallclock time not guaranteed to increase monotonically

neilconway commented 13 years ago

The first point is just message batching, isn't it? i.e., if we allow bunches of network events to co-occur, for similar reasons we might be inclined to allow bunches of clock events to co-occur.

neilconway commented 12 years ago

In 08d1a94dac, I added a description of the semantic guarantees we provide for periodics (that is, essentially none). Allowing > 1 periodic event per timestamp seems a natural consequence of allowing event batching in general -- AFAIK there is nothing left to do here. Closing, but reopen if you think we need to do more.