Use all bus data about onemta HOT 10 CLOSED

Use similar binary search implemented in #90 against bus line not possible

Store raw data in cache, DO NOT STORE OBJECTS; will cause memory issues.

< 10,000 busses

https://bt.mta.info/wiki/Developers/SIRIVehicleMonitoring

Please note that the calls made without either a VehicleRef or LineRef produces quite a load on the system, so use them sparingly. Any developers found to be making repeated calls (e.g. at less than 30 second intervals) for all vehicles in the system may find their key revoked.

from onemta.

Only this subclass needs to be modified

Stop monitoring should derive values from vehicle request if possible.

from onemta.

JSON parser needs to be massively optimized to avoid memory issues; use JIT (just-in-time) parsing, where we load immediate keys into memory, then parse the subsequent object when requested.

This count needs to be optimized to only run once: not possible due to split logic

https://sites.google.com/site/gson/streaming

https://stackoverflow.com/a/11876086

Regex may actually be more inefficient since we are rescanning the string multiple times. Use character loop stream instead.

Return a method to parse for:

and

from onemta.

@mashiro-san create a branch upgrade-json

from onemta.

@Katsute I have created a new branch upgrade-json@f3dfe30

from onemta.

• get methods need to be optimized so synchronized isn't blocking threads
• pull bus stop alert info from gtfs feed
• derive stop vehicles from all vehicles

from onemta.

Use CopyOnWriteArrayList to allow concurrent reads and locked writes.

ConcurrentMap?

In order to make write thread safe, have synchronized write block also check if its expired before fetching (any current active writes will make the result not expired, any queued writes will see that the resource is no longer expired and will return the new one instead).

Get first then check if expired to prevent concurrency issues.

from onemta.

@mashiro-san create a new branch upgrade cache

from onemta.

@Katsute I have created a new branch upgrade-cache@ebf9c8e

from onemta.

Possibly use #100 to implement this.

from onemta.