I was struggling with Subscriptions over HTTP for a whole day,
and this was the missing piece I was needing for getting forward.
I’d suggest making this info more explicit in the docs.
e.g When using HTTP API the developer is responsible for the whole client subscription implementation,
such as (normal/long) polling, the ‘prev’ link in the atom feed, etc. (with some cURL examples as other stuff).
I’m already here so maybe you could sort out one thing for me-
When following the atom feed, why should i watch the ‘prev’ link (and not the ‘next’ link)?
Am I going forward or backwards on this atom feed?
I’ll be happy if someone could elaborate or reference me to the right place to read at.
Thanks for this answer, and thanks for this awesome product.
Six months ago I started a journey, diving deep into DDD / ES / CQRS, Today I feel like you are my mentor (i’m sure others feel that way as well).
I started implementing Eventstore on my main greenfield project (used Kafka until now), and it feels amazing.
The only thing that’s a bit weird is the Documentation part, which I have a lot of feedback for, but that’s for another post,
the nice side of that is it forces me to jump into source code and actually -think-
Thanks for all you’ve given and giving to the software community.
Hope to say hi at upcoming DDD Europe