<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Il giorno 19/gen/08, alle ore 14:42, Christopher Schmidt ha scritto:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br>Does this help answer your questions? In general, I consider WFS a<br>relative 'corner case' -- OpenLayers users seldom use it compared to the<br>number of WMS users, for exactly the reasons you describe, so I<br>apologize if my first email was less than clear.</blockquote><div><br class="webkit-block-placeholder"></div>Christopher: thanks a lot, you are absoutely clear in explaining these architecture-related stuff. And yes, of course this helps me understand, for example that i must embed my application server in the same environment of Openlayers btw, using geoserver will make things a lot easier I think.</div><div><br class="webkit-block-placeholder"></div><div>Anyway what made me think of an ansynchronous interaction with the server was the fact that when you click on the examples, in every demo i tried I noticed that some information was displayed on an html table below the map. If I understand correctly what you tell, me, all information displayed are cached, or copied if you prefer in javascript variables?<br></div><br><div>My application set (a routing application I'm projecting for my graduating thesis) is postgis and geoserver. Now I'm trying to understand if this will be enough or if I need to setup a further layer of a web application server that interacts with geoserver for the functionality I need to extend.</div><div><br class="webkit-block-placeholder"></div><div>--</div><div><br class="webkit-block-placeholder"></div><div>Andrea Maschio<br><a href="http://www.superandrew.it/">http://www.superandrew.it</a></div></body></html>