The way the mapping industry grew up, depended on counting transactions. A transaction is either (a) a geocoding request/response, a routing request response, a search request response or 8 map tiles (256 x 256 pixels). Transactions still have their place for stateless APIs, but we’re moving on by introducing the concept of a session. Sessions will be used with the Bing Maps AJAX Map Control and the Bing Maps Silverlight Control. A session is basically defined as loading the map control and exploring at will – no tile limitations. I’m going to make it as clear and simple as I can, so here goes:
- Bing Maps AJAX Control – all maps rendered onto the client upon the initial request is considered 1 session. Session includes any requests for geocoding, routing or search.
- Bing Maps Silverlight Control – all maps rendered onto the client upon the initial request is considered 1 session. There are no services built into the Bing Maps Silverlight Control, so you would use the Bing Maps Web Service for geocoding, routing and search, but we’ll include those too.
- Bing Maps Web Service – all maps, geocodes, routes and searches will each invoke 1 transaction.
If you still have questions or don’t see where you fit into a category, visit our new licensing page.
CP – Follow me on Twitter @ChrisPendleton