You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The go-chi HTTP router used in the Watermill HTTP overrides added handlers for the same route. Because of that when calling httpSubscriber.Subscribe(ctx, url) with the same url N times it will invoke added HTTP handlers only once. Simple use case for the CQRS component with queue per package name not per packageName.CommandName/EventName. Received message from HTTP client will be delivered randomly only to one of registered command or event handler with the same topic name not to all added handlers. In that case the Watermill HTTP doesn't work as pub/sub.
The text was updated successfully, but these errors were encountered:
I have prepared Pull Request with necessary fixes for this issue ThreeDotsLabs/watermill-http#10 I don't know why CI fails for go build ./.... Locally it works perfectly fine without any problems.
tymonx
changed the title
[watermill-http] It doesn't support multi subscribe for the same single topic
[watermill-http] It doesn't support multi subscribes for the same single topic
Apr 12, 2022
The go-chi HTTP router used in the Watermill HTTP overrides added handlers for the same route. Because of that when calling
httpSubscriber.Subscribe(ctx, url)
with the sameurl
N times it will invoke added HTTP handlers only once. Simple use case for the CQRS component with queue per package name not perpackageName.CommandName/EventName
. Received message from HTTP client will be delivered randomly only to one of registered command or event handler with the same topic name not to all added handlers. In that case the Watermill HTTP doesn't work as pub/sub.The text was updated successfully, but these errors were encountered: