Ok i need the weekend off for once, im going to revert to 0.5 tarball
just for the weekend and come back to it monday, hopefully my reports
help.
Dan Rossi wrote:
this is really strange im getting bufferunderflow errors, for 300k
stream files but our 768k stream files are ok, some dont even stream at
all just hang.
this is with and without a cache.
Mondain wrote:
Basically it will try to first allocate the amount of
space needed to read the entire file. This is tune-able as far as using
heap buffers or direct buffers go. Please note that this "fix" is not
currently in RC1 though as I changed the handling after the release.
The code in 0.6 previous to my fix attempted to "wrap" the bytes from
the supplied file input stream without letting the implementer select
heap or direct, nor did the code first attempt to allocate space for
the file being read. What is the requested strategy for these ginormous
files? With files over two gigabytes we are going to have issues in
Java...
Paul
On 11/3/06, Owen van Dijk <[EMAIL PROTECTED]>
wrote:
What
exactly does Red5 do with large FLV files? It reads them all in
memory? Because we have an archive of over 600 very large FLV files (
some reaching the 1 gig mark ) and i'm wondering if anyone has tested
with such large files :)
--
Owen van Dijk
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
--
The early bird may get the worm, but the second mouse gets the cheese.
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
|
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
