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

Make use of SW since_id field on /feed requests #89

Open
haku opened this issue Aug 4, 2013 · 6 comments
Open

Make use of SW since_id field on /feed requests #89

haku opened this issue Aug 4, 2013 · 6 comments

Comments

@haku
Copy link
Owner

haku commented Aug 4, 2013

Finally make use of ianrenton/successwhale-api#25.

@haku
Copy link
Owner Author

haku commented Aug 4, 2013

done pending testing.

@haku
Copy link
Owner Author

haku commented Aug 5, 2013

<error>since_id parameter is invalid</error> on mixed feed requests, hmm...

@ianrenton
Copy link
Contributor

Unfortunately this is a bit more complicated than I thought. The error comes from Twitter when the since_id provided is not in the timeline requested, so a since_id will only normally be valid for one timeline. Not sure how best to handle this.

@haku
Copy link
Owner Author

haku commented Aug 9, 2013

Hmm.... might take this out of OS for the time being then.
Edit: I have done.

@haku
Copy link
Owner Author

haku commented Mar 28, 2014

Is this worth attempting to solve, or to complex to be worth it?
Only reliable solution I can think of involves posting all the recent item IDs and last updated dates (as many as max items wanted in response) so the the server can dedup before responding.

@ianrenton
Copy link
Contributor

I don't have a decent way to implement this server-side either, so I'm
happy for this one to be dropped or bumped down to lowest priority. I'm
not really sure we'd save a lot of processing time or bandwidth by
doing this anyway.

@haku haku added this to the Distant Future milestone Mar 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants