MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Spezifikationen Seite 361

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 369
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 360
Server-Side Communication ActionScript 61
reset A Boolean value that flushes the playing stream. If reset is false, the server maintains a
playlist, and each call to
Stream.play is appended to the end of the playlist so that the next play
does not start until the previous play finishes. You can use this technique to create a dynamic
playlist. If
reset is true, any playing stream stops, and the playlist is reset. By default, the value is
true. This is an optional parameter.
remoteConnection A reference to a NetConnection object that is used to connect to a remote
server. The requested stream plays from the remote server if this parameter is provided. This
parameter is optional.
Returns
A Boolean value: true if the Stream.play call is accepted by the server and added to the playlist;
false otherwise. The Stream.play method can fail if the server fails to find the stream or if an
error occurs. To get information about the
Stream.play call, you can define a Stream.onStatus
handler to catch the play status or error.
If the
streamName parameter is false, the stream stops playing. A Boolean value of true is
returned if the stop succeeds;
false otherwise.
Description
Method; controls the data source of a stream with an optional start time, duration, and reset flag
to flush any previously playing stream. The Stream.play method also has a parameter that lets
you reference a NetConnection object to play a stream from another server. The
Stream.play
method allows you to do the following:
Chain streams between servers.
Create a hub to switch between live streams and recorded streams.
Combine different steams into a recorded stream.
You can combine multiple streams to create a playlist for clients. The server-side
Stream.play
method behaves a bit differently than the
NetStream.play method on the client side. A play call
on the server is similar to a publish call on the client. It controls the source of the data that is
coming into a stream. When you call
Stream.play on the server, the server becomes the
publisher. Because the server has a higher priority than the client, the client is forced to unpublish
from the stream if the server calls a
play method on the same stream.
In general, if any recorded streams are included in a server playlist, you cannot play the server
stream as a live stream.
Note: A stream that plays from a remote server by means of the NetConnection object is a live stream.
If you require a value to begin a stream, you may need to change the Application.xml files
“Enhanced seeking” flag at the server. “Enhanced seeking” is a Boolean flag in the
Application.xml file. By default, this flag is set to
false. When a play occurs, the server seeks to
the closest video keyframe possible and starts from that keyframe. For example, if you want to
play at time 15, and there are keyframes only at time 11 and time 17, seeking will start from time
17 instead of time 15. This is an approximate seeking method that works well with compressed
streams.
If the flag is set to
true, some compression is invoked on the server. Using the previous example,
if the flag is set to
true, the server creates a keyframe—based on the preexisting keyframe at time
11—for each keyframe from 11 through 15. Even though a keyframe does not exist at the seek
time, the server generates a keyframe, which involves some processing time on the server.
Seitenansicht 360

Kommentare zu diesen Handbüchern

Keine Kommentare