<?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>topic Re: Can GeoEvent support sychronous messaging to avoid out of order issue? in ArcGIS GeoEvent Server Questions</title>
    <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/can-geoevent-support-sychronous-messaging-to-avoid/m-p/1107359#M3642</link>
    <description>&lt;P&gt;Hello William --&lt;/P&gt;&lt;P&gt;The inbound connectors you configure assume that they will receive the latest avilable data from a sensor network in real-time or near-real-time. Fundamental assumptions are that data will arrive in temporal order, at some discrete frequency and periodicity. Data should not be sent in batches with data records potentially out-of-temporal-order. GeoEvent Server can receive batches of data, but the batch is assumed to be a collection of individual observations from discrete sensors, not a collection of observations from a single sensor.&lt;/P&gt;&lt;P&gt;You might want to look into using SDK samples available on the &lt;A href="http://links.esri.com/geoevent-gallery" target="_self"&gt;GeoEvent Server Gallery&lt;/A&gt; to supplement your solution. The&amp;nbsp;&lt;A href="https://www.arcgis.com/home/item.html?id=1e37ccff6b764227b517b69c9dd98a36" target="_self"&gt;Delay Processor for GeoEvent Server&lt;/A&gt; or the&amp;nbsp;&lt;A href="https://www.arcgis.com/home/item.html?id=95cffd6166f948a69a946ae5dc862817" target="_self"&gt;Timetree Processor for GeoEvent Server&lt;/A&gt; may allow you to receive a collection of data observations, hold the data for a specified amount of time (e.g. "delay processing") and sort the data by TRACK_ID into a proper temporal order to guarantee processed event records reflect a first-in / first-out view of data collected from sensors in time order.&lt;/P&gt;&lt;P&gt;If you need help working with these SDK samples, please open an incident with Esri Technical Support. Limited consulting is available through technical support. More in-depth help implementing a solution can be arranged through Esri Professional Services if needed.&lt;/P&gt;&lt;P&gt;Hope this information helps&lt;BR /&gt;-- RJ&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 14 Oct 2021 00:08:16 GMT</pubDate>
    <dc:creator>RJSunderman</dc:creator>
    <dc:date>2021-10-14T00:08:16Z</dc:date>
    <item>
      <title>Can GeoEvent support sychronous messaging to avoid out of order issue?</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/can-geoevent-support-sychronous-messaging-to-avoid/m-p/1107131#M3639</link>
      <description>&lt;P&gt;Because sequence of messages is critical concern to us, can GeoEvent support synchronous messaging in some way to avoid out of order issue? In my understanding,&amp;nbsp;GeoEvent is an asynchronous product to increase throughput.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Oct 2021 15:55:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-questions/can-geoevent-support-sychronous-messaging-to-avoid/m-p/1107131#M3639</guid>
      <dc:creator>WilliamYip</dc:creator>
      <dc:date>2021-10-13T15:55:21Z</dc:date>
    </item>
    <item>
      <title>Re: Can GeoEvent support sychronous messaging to avoid out of order issue?</title>
      <link>https://community.esri.com/t5/arcgis-geoevent-server-questions/can-geoevent-support-sychronous-messaging-to-avoid/m-p/1107359#M3642</link>
      <description>&lt;P&gt;Hello William --&lt;/P&gt;&lt;P&gt;The inbound connectors you configure assume that they will receive the latest avilable data from a sensor network in real-time or near-real-time. Fundamental assumptions are that data will arrive in temporal order, at some discrete frequency and periodicity. Data should not be sent in batches with data records potentially out-of-temporal-order. GeoEvent Server can receive batches of data, but the batch is assumed to be a collection of individual observations from discrete sensors, not a collection of observations from a single sensor.&lt;/P&gt;&lt;P&gt;You might want to look into using SDK samples available on the &lt;A href="http://links.esri.com/geoevent-gallery" target="_self"&gt;GeoEvent Server Gallery&lt;/A&gt; to supplement your solution. The&amp;nbsp;&lt;A href="https://www.arcgis.com/home/item.html?id=1e37ccff6b764227b517b69c9dd98a36" target="_self"&gt;Delay Processor for GeoEvent Server&lt;/A&gt; or the&amp;nbsp;&lt;A href="https://www.arcgis.com/home/item.html?id=95cffd6166f948a69a946ae5dc862817" target="_self"&gt;Timetree Processor for GeoEvent Server&lt;/A&gt; may allow you to receive a collection of data observations, hold the data for a specified amount of time (e.g. "delay processing") and sort the data by TRACK_ID into a proper temporal order to guarantee processed event records reflect a first-in / first-out view of data collected from sensors in time order.&lt;/P&gt;&lt;P&gt;If you need help working with these SDK samples, please open an incident with Esri Technical Support. Limited consulting is available through technical support. More in-depth help implementing a solution can be arranged through Esri Professional Services if needed.&lt;/P&gt;&lt;P&gt;Hope this information helps&lt;BR /&gt;-- RJ&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Oct 2021 00:08:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-geoevent-server-questions/can-geoevent-support-sychronous-messaging-to-avoid/m-p/1107359#M3642</guid>
      <dc:creator>RJSunderman</dc:creator>
      <dc:date>2021-10-14T00:08:16Z</dc:date>
    </item>
  </channel>
</rss>

