I see these config options disabled are these important ?

    <!--
                <property name="tcpNoDelay" value="true"/>
                <property name="sendBufferSize" value="1024"/>
                <property name="receiveBufferSize" value="1024"/>
                <property name="soLinger" value="10"/>
                <property name="oobInline" value="false"/>
                <property name="keepAlive" value="true"/>               
                 -->

//cfg.setReceiveBufferSize(256);
        //cfg.setSendBufferSize(256);
        log.info("Is tcp delay enabled: " + cfg.isTcpNoDelay());
        cfg.setTcpNoDelay(true);
        super.sessionOpened(session);

and this in rtmpminaiohandler.java

Dan Rossi wrote:
> "The only time I see frozen frames is when I'm using live streams
>
> published by the Flash player itself.  These seem to result from one of
> the RTMP classes complaining about a negative timestamp (I keep meaning
> to investigate, but I haven't had a chance to delve into Red5's inner
> workings yet).
>
> Outside of the RTMP negative timestamp and an unhandled ping whenever
> someone connects to a live stream (which might be the reason liveDelay
> returns 0), Red5 is completely well behaved and the only issues I have
> are my typos  ;) "
>
> I get all these too, negative timestamp messages, unhandled ping, live delay 
> has always been 0. Could this be the problem ? We are publishing with a flex 
> client yes, is it something wrong im doing in the code ?
>
>
>
>
> _______________________________________________
> 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

Reply via email to