I think your maybe making too many requests to the server,
particularly over a network that may be spotty while driving.
Add to that the speed of the car and you have a problem.
Actually because the car is moving in a straight line, you can do a
single query for the next N kilometeres. you only
The data is speed limit signs. I think its time I switch to a local
copy like Jonathan said. I noticed there are tons of sort routines, so
I probably don't need sqlite...
Thanks guys!
cellurl
On Jan 15, 2:47 am, Jonathan Foley jonefo...@gmail.com wrote:
Why don't you pull down data ahead of
Alright.. little confused Speed limit signs? Every 50 meters a driver passes
one? Or you're trying to pull down speed limit data to let the user know
what speed they are supposed to be traveling (and thus if they are going
over the speed limit)?
Like others said.. is there some way you can pull
I would suggest being more flexible about *when* the queries are made. You
seem to have fixated on every 50 meters. Why not every two minutes? Or every
n minutes, depending upon the current network latency? Or even a heuristic
scheduler based on multiple factors? I would also suggest considering
Why don't you pull down data ahead of time? You haven't told us
exactly what you are querying.
Maps, logging the route?? In any case, you can either pre-cache some
of the data you'll need or cache
the data you'll be sending and send it less frequently in either
direction. The only reason I can
Well50 mph is about 22 m/s - so driving at that speed in a
straight line you are firing web queries off at the rate of
approximately 1 every 2 seconds. Running sql queries over the web on
a 3G network I'm not really surprised that the app locks up and has
lag.
Why not write a little app to
6 matches
Mail list logo
