Author Topic: taxi robbing  (Read 6748 times)

Offline Rat Catcher

  • Hero Member
  • *****
  • Posts: 26799
  • Karma: +34/-65535
  • Part Time Amateur Scum
Re: taxi robbing
« Reply #15 on: January 02, 2018, 04:00:25 pm »
Yeah, the app was shite last night, offering me jobs long after I had pressed busy, over a minute in 2 cases to accept the inputted fare, at one stage I turned it off and when I logged back on it showed me I was on a job 16km away!!! For Ireland’s largest dispatcher (by a country mile) this shite really shouldn’t be happening.
On a side note, I recently got a job at a hotel, guy came out, well pissed, said “we’ll be a few mins bud, start the meter”... I did, and pressed “passenger onboard “ a few mins later he returned with a fresh full pint and said “we’ll just be a few mins bud” I was pissed but waited as the meter was running, then he came back out and started getting sick in from one of my car, I took off, couldn’t cancel the job as I had pressed passenger onboard, couldn’t Claim scrub and had to input a few € to clear myself, that shite wouldn’t be long making you turn off when it’s busy.

€1 is the min input. You can use the Help->Incorrect Fare option to reclaim the commission and/or claim the no contact fee... although I had two no contact fees declined since they automated processing. In one case it was down to the slow server responses. The client side timer on my app started when I pressed arrived but it took another two minutes of watching a bouncing car before the arrived event was recorded on the server hence the job start time recorded suggested that I only waited 3 minutes yet the counter on the app displayed the correct 5 minutes. Therefore I tend to agree that it's not viable during peak times without bonus payments.

The server doesn't cope well at busy times. That's mainly down to inefficient programming with far too much client-server interaction. As you note the app needs a server response to perform the simple task of loading the fukking fare input screen, one example of completely unnecessary communication, another being the arrived event mentioned above... all that could be recorded client side and processed together in one server call in the background without endlessly tying up the UI with poxy bouncing cars.
« Last Edit: January 02, 2018, 04:05:37 pm by Rat Catcher »
If it doesn't have a roof sign and door stickers it's not a taxi.

john m

  • Guest
Re: taxi robbing
« Reply #16 on: January 02, 2018, 04:08:37 pm »
You never said .Do you Like the bouncing car icon or should they change it ?

Offline Rat Catcher

  • Hero Member
  • *****
  • Posts: 26799
  • Karma: +34/-65535
  • Part Time Amateur Scum
Re: taxi robbing
« Reply #17 on: January 02, 2018, 04:26:45 pm »
They should eliminate it. All that processing should be done in the background. When I press the take payment button it should record the time and location on my device and immediately display the fare input screen. When I complete that it should tell me I'm free and post the data to the server in the background without bothering me with how long or how many attempts it takes, I don't need to know.
If it doesn't have a roof sign and door stickers it's not a taxi.

 


Show Unread Posts