search

atomist-attic / rug

DEPRECATED Runtime for Rugs
GNU General Public License v3.0
53 stars 13 forks source link

Do not set timestamp when UpdatableMessage is created #654

Closed ddgenome closed 7 years ago

ddgenome commented 7 years ago

Leave the message timestamp unset, allowing the rug runtime to set it when the message is actually sent.

Currently, if you create two instances of an UpdatableMessage with the same ID in close temporal proximity, you can lose messages as they may get the same timestamp and therefore the second one will not be considered "newer" than the older one.

Lawouach commented 7 years ago

Talking about it, what's the precision we can get down to? Sub-second would be ideal.

ddgenome commented 7 years ago

Milliseconds currently, and its not enough.

kipz commented 7 years ago

AFAIK - this is in master.