<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.reimers.dk/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Jacob Reimers Weblog : AJAX, Tutorial</title><link>http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/AJAX/Tutorial/default.aspx</link><description>Tags: AJAX, Tutorial</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator><item><title>Using JSON Script Services with the Map Control, basic</title><link>http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/2008/04/29/using-json-script-services-with-the-map-control-basic.aspx</link><pubDate>Tue, 29 Apr 2008 08:54:00 GMT</pubDate><guid isPermaLink="false">1d3a0a14-04fc-431f-b1ad-cb618ffb2326:1573</guid><dc:creator>jjrdk</dc:creator><slash:comments>4</slash:comments><comments>http://www.reimers.dk/blogs/jacob_reimers_weblog/comments/1573.aspx</comments><wfw:commentRss>http://www.reimers.dk/blogs/jacob_reimers_weblog/commentrss.aspx?PostID=1573</wfw:commentRss><description>This is a short intro to the basics of using JSON serialized ScriptServices with the Google Maps .NET Control. The control has classes optimized to JSON serialization in the Reimers.Map.JsonMap namespace and it register clientside functions to assist in converting the server response to Google Classes....(&lt;a href="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/2008/04/29/using-json-script-services-with-the-map-control-basic.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.reimers.dk/aggbug.aspx?PostID=1573" width="1" height="1"&gt;</description><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/Google+Maps/default.aspx">Google Maps</category><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/Tutorial/default.aspx">Tutorial</category><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/AJAX/default.aspx">AJAX</category><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/dotNet/default.aspx">dotNet</category></item><item><title>Dealing with Obscene Amounts of Markers</title><link>http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/2007/01/31/dealing-with-obscene-amounts-of-markers.aspx</link><pubDate>Wed, 31 Jan 2007 02:21:00 GMT</pubDate><guid isPermaLink="false">1d3a0a14-04fc-431f-b1ad-cb618ffb2326:323</guid><dc:creator>jjrdk</dc:creator><slash:comments>1</slash:comments><comments>http://www.reimers.dk/blogs/jacob_reimers_weblog/comments/323.aspx</comments><wfw:commentRss>http://www.reimers.dk/blogs/jacob_reimers_weblog/commentrss.aspx?PostID=323</wfw:commentRss><description>Dealing with obscene amounts of overlays (typically markers or extremely long and complex polylines) is not recommendable. Most importantly Google's underlying API becomes terribly slow when dealing with more than 200 markers and complex polylines can create odd effects when scrolling the map. But equally important is the impression for the reader. Who can actually absorb the information that lies in 1000 plotted markers? This tutorial shows an example of how to deal with large amounts of data by selectively fetching it from a database....(&lt;a href="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/2007/01/31/dealing-with-obscene-amounts-of-markers.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.reimers.dk/aggbug.aspx?PostID=323" width="1" height="1"&gt;</description><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/Google+Maps/default.aspx">Google Maps</category><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/Tutorial/default.aspx">Tutorial</category><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/AJAX/default.aspx">AJAX</category></item><item><title>Introducing the ClientGeocoder</title><link>http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/2006/12/12/introducing-the-clientgeocoder.aspx</link><pubDate>Tue, 12 Dec 2006 11:22:00 GMT</pubDate><guid isPermaLink="false">1d3a0a14-04fc-431f-b1ad-cb618ffb2326:114</guid><dc:creator>jjrdk</dc:creator><slash:comments>2</slash:comments><comments>http://www.reimers.dk/blogs/jacob_reimers_weblog/comments/114.aspx</comments><wfw:commentRss>http://www.reimers.dk/blogs/jacob_reimers_weblog/commentrss.aspx?PostID=114</wfw:commentRss><description>There are numerous services that provide geocoding of IP addresses, mostly for a fee. As I wrote about previously Microsoft has a free IP locator service that runs from a client. This makes server interaction with the data provided somewhat difficult. To overcome this in an easy way I put together a small control, ClientGeocoder, that performs the geocoding using the Microsoft service and then sends a callback to the server where the location can be used....(&lt;a href="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/2006/12/12/introducing-the-clientgeocoder.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.reimers.dk/aggbug.aspx?PostID=114" width="1" height="1"&gt;</description><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/Tutorial/default.aspx">Tutorial</category><category domain="http://www.reimers.dk/blogs/jacob_reimers_weblog/archive/tags/AJAX/default.aspx">AJAX</category></item></channel></rss>