Skip to content
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

Support of ATOM-feed #66

Open
coreation opened this issue Mar 31, 2012 · 1 comment
Open

Support of ATOM-feed #66

coreation opened this issue Mar 31, 2012 · 1 comment
Assignees

Comments

@coreation
Copy link
Member

As well as receiving, as publishing.

@ghost ghost assigned coreation Mar 31, 2012
@pietercolpaert
Copy link
Member

How are you going to implement this? Don't we need to keep a history of the resource then?

The idea behind Atom is that it's a "push"-mechanism. We however would have to pull internally, and then push externally, which is the wrong way of implementing push notifications.

Another idea could be to export timestamps to Atom. But this is a stupid idea as the dynamic data inside a body will get generated on every request, which gives no guarantees that between 2 calls, old data will remain the same. (for instance: a train gets delayed. Will this be a new item in your Atom feed?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants