[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-commit] [patch #8086] RTMP netStream patch

From: George Thomas
Subject: [Gnash-commit] [patch #8086] RTMP netStream patch
Date: Fri, 06 Sep 2013 13:55:03 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:21.0) Gecko/20100101 Firefox/21.0

Follow-up Comment #40, patch #8086 (project gnash):

This logically looks like a mistake but I am also surprised it is working. 

The rtmp object has a Socket attribute assosciated with it which is handling
the writing to the network. 
The creates the packet and writes to the socket. 

But I am surprised the initialization takes place at _rtmp.connect() which
gets called at the 
time of creation of connection. Ideally the objects used should be the same.

An error is seen in the logs.
ERROR: Socket send error Socket operation on non-socket

The problem in using the same object is that RTMPConnection is the one having
the rtmp object. So I believe the play method functionality also should go

The situation is like this

RTMPConnection(_rtmp object is present there)/HTTPConnection ---> Connection
NetConnection_as  uses (Connection)
NetStream_as (has NetConnection as its member)

So the problem is the accessing the _rtmp object in NetConnection from

The docs for Connection class says 

/// Abstract connection handler class
/// This class abstract operations on network connections,
/// specifically RPC and streams fetching.
class Connection : boost::noncopyable

So is this not the right place to have the play method as well?

netstream_play is the entry point for netstream from the actionscript as I
understand it. And this is from where the play of the netStream is actually


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]