>I think I have these resources in order from most significant to least >significant for the average app store app. So when he says >"client-side", I'm starting to wonder because client-server apps are >generally less responsive and require more mobile bandwidth, consuming >2 precious resources.
I mean a mobile app which would generally work standalone, but could, if desired, download data from a server. This would not happen very often and maybe not at all. So fast communication with the server is not essential. When I asked my original question I was really just wanting to see if there was some agreement on a standard data transfer/storage format for OSM data in point/polyline (i.e. osm2pgsql output) so that I could use that rather than roll my own. The question was less concerned about how the data would be stored internally in the app. Thanks for the replies, got some useful ideas. Nick -----Nic Roets <nro...@gmail.com> wrote: ----- To: Tim Teulings <t...@framstag.com> From: Nic Roets <nro...@gmail.com> Date: 17/02/2011 07:23PM Cc: dev@openstreetmap.org Subject: Re: [OSM-dev] OSM formats optimised for client-side vector rendering? On Thu, Feb 17, 2011 at 7:02 PM, Tim Teulings <t...@framstag.com> wrote: > There is always a > trade of :-/ Absolutely. I think Nick refers to mobile users, in which case the tradeoffs are (a) the time of the user (b) mobile bandwidth (c) processing power, i.e. must the user buy a faster phone to run the app (d) RAM (e) flash (f) Wlan bandwidth that is often available at home / work. I think I have these resources in order from most significant to least significant for the average app store app. So when he says "client-side", I'm starting to wonder because client-server apps are generally less responsive and require more mobile bandwidth, consuming 2 precious resources. _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
_______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
