MACROMEDIA FLASH MEDIA SERVER 2-USING FLASH MEDIA SERVER EDGE SERVERS Bedienungsanleitung Seite 6

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 9
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 5
2817937
To exclude x-comment from appending to the logging fields use the new attribute
<Fields disable_extra_comment="true"> in the Logger.xml under Access ->
Fields:disable_extra_comment="true".
2807007
Added a default Application.xml to the multicast server-side sample application to
disable queuing and aggregate messages.
2766887
The files application.asc, facade.asc, and framework.asc belong to the deprecated
server-side components framework in the scriptlib folder have been removed in this
release.
2674905
In an n-tier deployment where multiple live streams with different bitrates are being
multi-point published from the ingest node to a downstream node, (and
synchronized keyframes as required for seamless switching when dynamic
streaming), if the streams are being recorded at the downstream node with the
intention of utilizing them as DVR streams, the value of "AssumeAbsoluteTime"
configuration in application.xml should be set to "true" for the application at the
downstream node where the recording is taking place.
2633530
CGI not supported in the Flash Media Server Apache installation.
2623244
It is not recommended to proxy HTTP Streaming traffic destined for the Apache web
server through Flash Media Server. There are known issues where HTTP connections
hang when proxying through the server. It is recommended that the web server be
reached directly through its own port (default is port 8134), or that the FMS is not
configured to use port 80.
2501913
Authorization and Access plugins have compilation warnings that are harmless.
Removing the warnings now would require an interface change breaking
compatibility with pre-existing plugins that were built using the current interface. To
maintain compatibility and not require users to have to rebuild and retest their
existing plugins, we have decided not to fix these warnings at this time.
2482789
By default, clients use port 1935 and ports 19350-65535 to communicate with Flash
Media Server over the RTMFP protocol. Clients connect to the server over 1935 and
the server migrates the socket to a port between 19350 and 65535. The server
migrates the first client that connects to an application to port 19350. The server
migrates the next client to port 19351, and so on. To change the default RTMFP
migration ports, edit the Adaptor/RTMFP/Core/HostPortList/HostPort element in the
Adaptor.xml configuration file.
2275665
sc-stream-bytes measures the bytes per stream sent from server to client for a
particular client. Note, that when compared with sc-bytes, which measures all bytes
sent from server to client for a particular client, users may notice a discrepancy. The
sum total of all sc-stream-bytes for a particular client will usually be. There are a
number of situations that could trigger this discrepancy, but users are advised to
take note of this if trying to use sc-stream-bytes for billing purposes. Billing should
be done based on sc-bytes when possible. I’ll add this to the docs, FWIW.
1931450
The MP4/F4V format delivers XMP text under the wrong tag. Specifically MP4/F4Vs
parsed by Flash Media Server or Flash Player (via Progressive Download Playback)
will produce onXMPData messages containing their XMP text under the tag
onXMPData/data. The correct tag is onXMPData/liveXML as specified by XMP
definitions. FLV container format renders this data correctly. Users should be
prepared for this difference in XMP reporting according to file format change.
Note: customers should test the new XMP ActionScript libraries at:
Seitenansicht 5
1 2 3 4 5 6 7 8 9

Kommentare zu diesen Handbüchern

Keine Kommentare