Events published in same millisecond aren't seen by clients about golongpoll

[jcuga]

@concreted this is absolutely a bug. The real fix would be to use a counter instead of timestamp to pick up where the previous longpoll results left off, but that would be a breaking change to any existing clients.

I will see if I can come up with a fix that still allows clients to use the since_time query parameter that doesn't require major refactoring.

I plan on revisiting this library and making a new version addressing all of the feedback I've received thus far, so if I can't find an easy fix for this now, then it will be addressed in the next major version.

Thanks for reporting this.

[jcuga]

Fixed in v1.3.0

[jcuga]

The fix requires using the new last_id subscription request parameter (documented in HttpLongPollAPI.md).

The updated golang client and new js-client already use this new param Only custom clients will need to update to use this to get the fixed behavior.