Content pull

From SpinetiX Support Wiki

Jump to: navigation, search

Although retrieving individual remote resources can also be seen as content pull, this page focuses on the retrieval of multiple resources or an entire project.


Content pull is a content management method employed when one or more HMP devices need to retrieve content from a remote content server via HTTP(S).

There are many reasons for using a content server, the most common being:

  • Direct network access is not possible for pushing the content on the HMP, for instance the HMP is in a private network using firewall / NAT.
  • The new content has to be pushed on the HMP according to a fixed schedule.
  • Parts of the content are managed by different persons who do not have access to the player content in order to avoid accidental changes. In this case, the new content is uploaded on a content server (e.g., local web server, Box etc.) and the HMP retrieves it from there. See also content delegation page.


The HMP can retrieve content from a content server through one of the following methods:

Methods Description Advantages Disadvantages
Scheduled Download,

Pull Mode

The HMP first retrieves the content onto its local storage and then plays it from there. The download can be triggered manually, according to a schedule, or using RPC commands.
  • Resilience to network failures.
  • A slow network connection can be used.
  • Content pull is skipped if the server is not accessible.
  • The content might not be the very latest.
Live Sources,

Client/Server mode

The HMP plays the content stored on a remote content server, directly from there. Each resource is verified & retrieved when it needs to be played; some resources might be cached locally to minimize the network bandwidth.
  • "Live" content playing.
  • Not resilient to network failures and the server needs to be accessible at any time.
  • The network connection needs to be (very) fast.


This page was last modified on 8 January 2018, at 16:17.