Elements with an [up-poll] attribute are reloaded from the server periodically.
Example
Assume an application layout with an unread message counter.
You can use [up-poll] to refresh the counter every 30 seconds:
<div class="unread-count" up-poll>
2 new messages
</div>
Controlling the reload interval
You may set an optional [up-interval] attribute to set the reload interval in milliseconds:
<div class="unread-count" up-poll up-interval="10000">
2 new messages
</div>
If the value is omitted, a global default is used. You may configure the default like this:
up.radio.config.pollInterval = 10000
Controlling the source URL
The element will be reloaded from the URL from which it was originally loaded.
To reload from another URL, set an [up-source] attribute on the polling element:
<div class="unread-count" up-poll up-source="/unread-count">
2 new messages
</div>
Skipping updates when nothing changed
When polling a fragment periodically we want to avoid rendering unchanged content.
This saves CPU time and reduces the bandwidth cost for a
request/response exchange to ~1 KB.
To achieve this we timestamp your fragments with an [up-time] attribute to indicate
when the underlying data was last changed. See [up-time] for a detailed example.
