New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Group by service path in initial notifications #2437

Open
fgalan opened this Issue Aug 4, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@fgalan
Copy link
Member

fgalan commented Aug 4, 2016

Current behaviour: initial notification Fiware-ServicePath header is a list of comma-separated items, each one corresponding to an entity in the payload (remember that initial notifications may include several entities).

New behaviour: instead of sending 1 notification, send as many notifications as different service paths. Each notification will include a single item in the Fiware-ServicePath and all the entities that belong to that service path.

This way we could improve CB integrations with receptor that are prepared to process single-item Fiware-ServicePath headers, but that has problems when the header includes a list.

@fgalan fgalan added the backlog label Aug 4, 2016

@fgalan fgalan changed the title Grouping by service path in initial notifications Group by service path in initial notifications Aug 4, 2016

@fgalan

This comment has been minimized.

Copy link
Member Author

fgalan commented Oct 20, 2017

federation.md document now includes a paragraph regarding potential problems with the initial notification. That paragraph should be adapted once this issue gets completed, or maybe even removed.

@fgalan

This comment has been minimized.

Copy link
Member Author

fgalan commented Oct 23, 2017

initial_notification.md#additional-considerations should be adjusted once this issue gets completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment