[
https://issues.apache.org/jira/browse/QUARKS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252432#comment-15252432
]
ASF GitHub Bot commented on QUARKS-123:
---------------------------------------
Github user dlaboss commented on a diff in the pull request:
https://github.com/apache/incubator-quarks-website/pull/40#discussion_r60633997
--- Diff: site/recipes/recipe_adaptable_polling_source.md ---
@@ -0,0 +1,138 @@
+---
+title: Changing a Polled Source Stream's Period
+---
+
+The [Writing a Source Function](recipe_source_function.html) recipe
introduced the basics of creating a source stream by polling a data source
periodically.
+
+Oftentimes, a user wants the poll frequency to be adaptable rather than
static. For example, an event such a sudden rise in a temperature sensor may
motivate more frequent polling of the sensor and analysis of the data until the
condition subsides. A change in the poll frequency may be driven by locally
performed analytics or via a command from an external source.
+
+A Quarks IotProvider and IoTDevice with its command streams would be a
natural way to control the application. In this recipe we will just simulate a
"set poll period" command stream.
--- End diff --
done
> Add recipe for poll() source with adaptable poll rate
> -----------------------------------------------------
>
> Key: QUARKS-123
> URL: https://issues.apache.org/jira/browse/QUARKS-123
> Project: Quarks
> Issue Type: Task
> Components: Documentation
> Reporter: Dale LaBossiere
> Assignee: Dale LaBossiere
>
> A use case is something like: an application wants to increase the poll
> frequency / rate of analytics once some trigger condition occurs. The
> trigger condition may be detected by local analytics. Or perhaps the change
> in poll frequency will be the result of receiving an IotDevice command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
