search

dccabs / pair

Pair project
0 stars 0 forks source link

how to handle when api is down. #9

Open dccabs opened 7 years ago

dccabs commented 7 years ago

What kind of error's do we want to show when the PAIR public API is down?

we should figure this out, because otherwise people are just going to think this site isn't working when really it's the api that is down.

clmulk commented 7 years ago

Hey, Dan. Sorry for not paying much attention to this yet, but i AM very excited about it. in terms of API being down, I've got a few thoughts. (1) Simple message that states that it's down and to check back shortly. (2) Simple message that states it's down, and an option to have the system send you (a) either an basic notification saying it's back up, or even cooler, the results you want based on the initial query.

I was wondering what it would take to have the data on a server, possibly JUST the data on status minus all the other data one can normally find, for when the API is down. But I'm guessing that would open up a whole other can of worms.

The good thing about the notification of API being down is that at least we know visitors to the site won't be able to just go somewhere else to get it (some exceptions), so I don't think we'd be turning away interested traffic.

dccabs commented 7 years ago

Hey Chris,

well something interesting happened this afternoon. the pair bulk data site blocked my IP, at my house. I think I did too many requests today or over the past few days. I sent an email to them asking what the limit is to see if I can get an answer. In the meantime, i'm investigating downloading the bulk data file and creating our own API, and what's involved there. I'm not sure about the question about stripping out all the extra data that you don't want.

I'll give you guys an update when i find out more. But for right now i'm kind of stopped in my tracks.

-dan

On Wed, Feb 8, 2017 at 4:02 PM, clmulk notifications@github.com wrote:

Hey, Dan. Sorry for not paying much attention to this yet, but i AM very excited about it. in terms of API being down, I've got a few thoughts. (1) Simple message that states that it's down and to check back shortly. (2) Simple message that states it's down, and an option to have the system send you (a) either an basic notification saying it's back up, or even cooler, the results you want based on the initial query.

I was wondering what it would take to have the data on a server, possibly JUST the data on status minus all the other data one can normally find, for when the API is down. But I'm guessing that would open up a whole other can of worms.

The good thing about the notification of API being down is that at least we know visitors to the site won't be able to just go somewhere else to get it (some exceptions), so I don't think we'd be turning away interested traffic.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dccabs/pair/issues/9#issuecomment-278476111, or mute the thread https://github.com/notifications/unsubscribe-auth/AAiGX09l3LmU3WYceDLJUO17dd0gNrJHks5rajtegaJpZM4L7YEN .