(Much of this has been removed for
brevity.) Take note that the VE service implements the mapping functionality, returning
the correct map tiles upon requests from this client library.
First the browser issues the initial request to a page:
#1 10:34:27.328 127.0.0.1:4611
GET /chapter9/Default.aspx HTTP/1.1
Accept: */*
Accept-Language: en-us
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
Then the server responds with this:
#2 10:34:27.390 127.0.0.1:4611
HTTP/1.1 200 OK
Server: ASP.NET Development Server/8.0.0.0
Date: Mon, 21 May 2007 18:34:27 GMT
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 1624
Connection: Close
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
...
After the initial download of the page, the map control kicks in and starts making the
asynchronous requests for the map tiles using XMLHttpRequest. You can see the request,
issued by the map control:
#11 10:34:28.656 65.55.241.30:80
GET /tiles/r021230000.
Pages:
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305