Fast for single queries, not for batch geocoding? So a web query can come from a user of a web service, the external(?) geocoding API can be called -- and the

Fast for single queries, not for batch geocoding? So a web query can come from a user of a web service, the external(?) geocoding API can be called -- and the reply can go back to user [applying lon/lat processing] without waiting too long. (I don't do anything like this for a while, so please apply NaCl.)