As far as I can tell, the result of a GET like http://ws.geonames.org/findNearestAddressJSON?lat=37&lng=-122 is not allowed to be cached by http proxies. If the response indicated that it was cachable, then a standard http cache (e.g. squid) would be able to accelerate my app and take some load off your servers. As it stands, I have to write a custom cache to get the same effect.
Please consider setting an expiration time on your http results. I think it would have a big benefit for very little work.
All geonames web services set a no-cache header deliberatly and it is not planed to change this. The reduction of request would be minimal at the other hand there would be issues with stale caches.
![[Search]](/gforum/templates/default/images/icon_mini_search.gif){kind=icon}
![[Recent Topics]](/gforum/templates/default/images/icon_mini_recentTopics.gif){kind=icon}
![[Groups]](/gforum/templates/default/images/icon_mini_groups.gif){kind=icon}
![[Register]](/gforum/templates/default/images/icon_mini_register.gif){kind=icon}
Register![[Login]](/gforum/templates/default/images/icon_mini_login.gif){kind=icon}
Login
![[Post New]](/gforum/templates/default/images/icon_minipost_new.gif){kind=icon}
![[Up]](/gforum/templates/default/images/icon_up.gif){kind=icon}
![[WWW]](/gforum/templates/default/images/icon_www.gif){kind=icon}