[Red5] FLV stream cache phenomenon
viacontact at v-i-a.net
Thu Nov 17 14:21:07 EST 2005
> the flash player client connects to the server using binary sockets.
> This means that there is no http involved in the exchange of data.
> The flash player asks for the flv stream of bytes, and then stores it
> in memory and releases the memory as soon as the flv byte stream has
> been viewed. Progressive video on the other hand downloads a flv file
> to the browser cache like any other file through http and then plays
> that file.
but, when the player when the connection to FlashCom use the RTMPT
protocol, what happening ?
RTMPT is wrapped in http headers.
So how could the player behave to bypass the borwser cache ?
Is it just a fact of the binary socket ?
I know that the magic should be hidden inside the NetConnection class.
But it is also used for Flash Remoting.
Flash Remoting doesn't use binary socket, but AMF binary exchange.
So am I asking if it could possible to stream FLV on http without
caching by a way similar than remoting.
Follow me ?
More information about the Red5