Re:Introducing the Uber Request Endpoint
by MengerSponge on Tuesday March 17, 2015 @10:53PM
(#9223320)
This would be great! This is where people still hire cabs in my city--If you have an early flight, do you trust that there will be an Uber driver available? Or do you pay a little extra and call a cab service with a scheduled pickup?
The difficulty is that there's still no guarantee that an Uber would be available. It'd just take care of the request part. Would need to be some thinking around what if there's none available in the area etc.
Re:Introducing the Uber Request Endpoint
by toomuchtodo on Wednesday March 18, 2015 @12:04AM
(#9223534)
You mean a cron/at job with curl and json?
(cron repeats, at is for one time jobs)
Effectively, yeah. Thinking from the RoR world something like sidekiq or delayed_jobs could do the same thing.
Re:Introducing the Uber Request Endpoint
by toomuchtodo on Wednesday March 18, 2015 @12:42AM
(#9223653)
Should definitely work. I use a cron job in the winter to kick off the remote start on my wife's car through Viper/Directed's JSON API.
An example would be I know I'll need an Uber tomorrow morning at 7AM so rather than get out my phone at 6:50AM I do it the night before and it just delays the request until the morning? Perhaps even add in some push notifications or something to check that you still want to book it and all you have to do is hit yes/no.