google-code-export / red5

Automatically exported from code.google.com/p/red5
0 stars 0 forks source link

Context path missing in java connected scope #47

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Connect client to the root scope
2. In java, in the connect() method, create a child scope named 'room_1' ( at 
this point childScope.getContextPath() will return correctly '/room_1' )
3. In java, connect the client to this child scope and in the connect() method 
of this new child scope, print the scope.getContextPath(), it will be empty !

What is the expected output? What do you see instead?
'/room_1' is expected, but '' is returned.

What version of the product are you using? On what operating system?
Red5 standalone 1.0RC on debian. MultiThreadedApplicationAdapter is used ( 
don't know if that change something )

Please provide any additional information below.
In the roomJoin() method of the child scope, context path is correctly set...

Original issue reported on code.google.com by franck...@free.fr on 25 Feb 2011 at 4:04

GoogleCodeExporter commented 9 years ago
I have tried according to your steps:
First, I connect to my server using below url
rtmp://192.168.227.129/testred5
in the ChildScopeTestServer.java's connect method, I create child scope 
"client_1".
you can see the result in red5.log file line 3-8.

Second, I connect to server using below url
rtmp://192.168.227.129/testred5/client_1
you can find result in log file line 20- 31
in the second step, you could find that connect method called twice, the first 
time is to connect "testred5", the second call is to connect to "client_1".

Original comment by xuyan...@gmail.com on 18 Mar 2011 at 1:30

Attachments:

GoogleCodeExporter commented 9 years ago
What you did is not folowing the steps i described, don't reconnect the client 
to the new child scope, connect him in java just after creating the child scope.

Original comment by franck...@free.fr on 19 Mar 2011 at 11:06

GoogleCodeExporter commented 9 years ago
then attach your code please

Original comment by xuyan...@gmail.com on 19 Mar 2011 at 1:03

GoogleCodeExporter commented 9 years ago

Original comment by mondain on 25 Jul 2011 at 4:03

GoogleCodeExporter commented 9 years ago
Franck, what are you using to make these connections? Flash player or 
RTMPClient? Its not clear to me what is going on here and thus it would be 
difficult to fix. Like Xuyan asked, please attach some test code to help us fix 
this.

Original comment by mondain on 5 Aug 2011 at 5:15

GoogleCodeExporter commented 9 years ago
Closing due to confusion about how to reproduce the issue. No client code is 
actually required, a simple modification for the unit test "ScopeTest.java" 
under the test directory could assist us.

Original comment by mondain on 18 May 2012 at 1:03