<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Implement common Geometry Service operations in an HTML5 web worker process in Developers Ideas</title>
    <link>https://community.esri.com/t5/developers-ideas/implement-common-geometry-service-operations-in-an/idi-p/929289</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Better responsiveness of mobile JavaScript API apps.&lt;BR /&gt;&lt;BR /&gt;Some commonly used geometric operations could be written in JavaScript and used in an HTML5 web worker process.&amp;nbsp; This could be very useful for mobile web apps by reducing slow &lt;A href="http://dev.opera.com/articles/view/web-workers-rise-up/&amp;quot;"&gt;http://dev.opera.com/articles/view/web-workers-rise-up/"&lt;/A&gt;king mobile apps more responsive.&amp;nbsp; These could be created as a seperate set of widgets which can be requested on a 'per geometric operation' basis by apps which use the JavaScript API&amp;nbsp;compact build, thus keeping the &lt;A href="http://dev.opera.com/articles/view/web-workers-rise-up/&amp;quot;"&gt;http://dev.opera.com/articles/view/web-workers-rise-up/"&lt;/A&gt;tline the web worker process:&lt;BR /&gt;&lt;A href="http://dev.opera.com/articles/view/web-workers-rise-up/" target="_blank"&gt;http://dev.opera.com/articles/view/web-workers-rise-up/&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.sitepoint.com/javascript-threading-html5-web-workers/" target="_blank"&gt;http://www.sitepoint.com/javascript-threading-html5-web-workers/&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.sitepoint.com/javascript-large-data-processing/" target="_blank"&gt;http://www.sitepoint.com/javascript-large-data-processing/&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.sitepoint.com/javascript-shared-web-workers-html5/" target="_blank"&gt;http://www.sitepoint.com/javascript-shared-web-workers-html5/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;A typical example could be the buffer operation:&lt;BR /&gt;1)&amp;nbsp;User clicks a point and wants to perform a search for all related locations within 1km.&lt;BR /&gt;2)&amp;nbsp;Instead of creating a 1km buffer via the geometry service and waiting for the polygon to be sent back in a response, the app could create the buffer itself thus eliminating the HTTP&amp;nbsp;request for this step.&lt;BR /&gt;3)&amp;nbsp;The resulting buffer is then used to query either graphics on the map or a REST&amp;nbsp;query for a map service.&lt;BR /&gt;The above workflow would reduce the need for a 'synchronous' request to the Geometry Service and (depending on the level of connectivity) could result in a much more responsive process.&lt;BR /&gt;

&lt;!-- content transformation source ID: 08730000000bril --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Sep 2011 10:47:23 GMT</pubDate>
    <dc:creator>SamLarsen1</dc:creator>
    <dc:date>2011-09-22T10:47:23Z</dc:date>
    <item>
      <title>Implement common Geometry Service operations in an HTML5 web worker process</title>
      <link>https://community.esri.com/t5/developers-ideas/implement-common-geometry-service-operations-in-an/idi-p/929289</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Better responsiveness of mobile JavaScript API apps.&lt;BR /&gt;&lt;BR /&gt;Some commonly used geometric operations could be written in JavaScript and used in an HTML5 web worker process.&amp;nbsp; This could be very useful for mobile web apps by reducing slow &lt;A href="http://dev.opera.com/articles/view/web-workers-rise-up/&amp;quot;"&gt;http://dev.opera.com/articles/view/web-workers-rise-up/"&lt;/A&gt;king mobile apps more responsive.&amp;nbsp; These could be created as a seperate set of widgets which can be requested on a 'per geometric operation' basis by apps which use the JavaScript API&amp;nbsp;compact build, thus keeping the &lt;A href="http://dev.opera.com/articles/view/web-workers-rise-up/&amp;quot;"&gt;http://dev.opera.com/articles/view/web-workers-rise-up/"&lt;/A&gt;tline the web worker process:&lt;BR /&gt;&lt;A href="http://dev.opera.com/articles/view/web-workers-rise-up/" target="_blank"&gt;http://dev.opera.com/articles/view/web-workers-rise-up/&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.sitepoint.com/javascript-threading-html5-web-workers/" target="_blank"&gt;http://www.sitepoint.com/javascript-threading-html5-web-workers/&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.sitepoint.com/javascript-large-data-processing/" target="_blank"&gt;http://www.sitepoint.com/javascript-large-data-processing/&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.sitepoint.com/javascript-shared-web-workers-html5/" target="_blank"&gt;http://www.sitepoint.com/javascript-shared-web-workers-html5/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;A typical example could be the buffer operation:&lt;BR /&gt;1)&amp;nbsp;User clicks a point and wants to perform a search for all related locations within 1km.&lt;BR /&gt;2)&amp;nbsp;Instead of creating a 1km buffer via the geometry service and waiting for the polygon to be sent back in a response, the app could create the buffer itself thus eliminating the HTTP&amp;nbsp;request for this step.&lt;BR /&gt;3)&amp;nbsp;The resulting buffer is then used to query either graphics on the map or a REST&amp;nbsp;query for a map service.&lt;BR /&gt;The above workflow would reduce the need for a 'synchronous' request to the Geometry Service and (depending on the level of connectivity) could result in a much more responsive process.&lt;BR /&gt;

&lt;!-- content transformation source ID: 08730000000bril --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Sep 2011 10:47:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-ideas/implement-common-geometry-service-operations-in-an/idi-p/929289</guid>
      <dc:creator>SamLarsen1</dc:creator>
      <dc:date>2011-09-22T10:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: Implement common Geometry Service operations in an HTML5 web worker process</title>
      <link>https://community.esri.com/t5/developers-ideas/implement-common-geometry-service-operations-in-an/idc-p/929290#M237</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Also, another key requirement for me is working with projections in mobile JavaScript apps.&lt;BR /&gt;When working with British National Grid, i need to project my 'geolocation' each time i access it.&amp;nbsp; This is a big problem when i have to send a request back to the Geometry Service.&amp;nbsp; It would be fantastic if i could get a Geometry Service Web Worker which does a projection from one to the other.&amp;nbsp; I am sure this is also a requirement for many others who want to use their own projections in mobile web apps.&lt;BR /&gt;

&lt;!-- content transformation source ID: 00a3000000Bfmmg --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Sep 2011 10:55:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-ideas/implement-common-geometry-service-operations-in-an/idc-p/929290#M237</guid>
      <dc:creator>SamLarsen1</dc:creator>
      <dc:date>2011-09-22T10:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Implement common Geometry Service operations in an HTML5 web worker process</title>
      <link>https://community.esri.com/t5/developers-ideas/implement-common-geometry-service-operations-in-an/idc-p/929291#M238</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Excellent suggestion, was about to post the same idea when i saw this.&lt;BR /&gt;&lt;BR /&gt;The geometry service is not as scalable as client side geometric operations. It needs to be re-implemented on the client. HTML5 worker processes are a great suggestion.&lt;BR /&gt;&lt;BR /&gt;This is a must have to ensure highly efficient web GIS systems.&lt;BR /&gt;&lt;BR /&gt;

&lt;!-- content transformation source ID: 00a3000000E6mvk --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 01:22:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-ideas/implement-common-geometry-service-operations-in-an/idc-p/929291#M238</guid>
      <dc:creator>DanielBaternik</dc:creator>
      <dc:date>2012-02-27T01:22:23Z</dc:date>
    </item>
  </channel>
</rss>

