Cisco Cisco StadiumVision Mobile Reporter Manuel De Maintenance
© 2011-2012 Cisco Systems, Inc. All rights reserved.
Page 5 of 10
2. At 1:00:30 (every 30 seconds) the SV Director server checks for freshness of
data. It only refreshes data for which the refresh period has expired. Since the
refresh rate in this example is set to 45 seconds, the refresh period has not
expired. Therefore, the server hangs on to the new data until the next 30 second
interval hits.
refresh rate in this example is set to 45 seconds, the refresh period has not
expired. Therefore, the server hangs on to the new data until the next 30 second
interval hits.
3. At 1:01 (the next 30 second interval), the server does its check for freshness of
data. Since the refresh rate is set to 45 seconds and 1 minute has passed, the
refresh period for the data is considered “expired.” Therefore, the server sends
out new RSS data to the DMP.
refresh period for the data is considered “expired.” Therefore, the server sends
out new RSS data to the DMP.
Figure 1.
Refreshing Content
To protect against overflows in RSS feeds, StadiumVision Director trims the number
of RSS feed entries to a maximum message size of 15822 bytes. Each RSS ticker
text consumes the following number of bytes against this maximum:
of RSS feed entries to a maximum message size of 15822 bytes. Each RSS ticker
text consumes the following number of bytes against this maximum:
•
32 bytes of message traffic overhead per ticker text
•
The size of the ticker text, after percent encoding (also known as URL
the particular details of the specific characters which are and are not percent-
encoded are those enforced by the java urlencode function. See
encoded are those enforced by the java urlencode function. See
•
If more RSS data exists than can fit into the 15822 bytes, the data is truncated.
Extra entries will not be sent to the DMPs.