[Red5devs] Scope.connect
Saman Ghodsian
Saman.Ghodsian at alea.ca
Fri May 9 09:49:56 PDT 2008
Hi All,
We're implementing a solution based on red5 and had a question on the
Scope.connect method, we're seeing some unexpected behavior due to the
fact that when a connection is established to a scope, all the parent
scopes are also being connected.
*/
public boolean connect(IConnection conn, Object[] params) {
// logger.debug("Has connection: {}", (conn != null));
// logger.debug("Has handler: {}", (handler != null));
// logger.debug("Has parent: {}", (parent != null));
if (hasParent() && !parent.connect(conn, params)) {
return false;
}
We'd like to comment out the recursive connection, the question is what
would be the impact if any of doing so....
Thanks and great work!!
Saman
From: red5devs-bounces at osflash.org [mailto:red5devs-bounces at osflash.org]
On Behalf Of Mondain
Sent: Tuesday, May 06, 2008 4:50 PM
To: red5devs at osflash.org
Subject: Re: [Red5devs] Socket policy server error
Adobe picked the port.. :) and yes it is configurable. Go to
red5.properties and update "policy.port".
Paul
On Tue, May 6, 2008 at 1:48 PM, Daniel Rossi <spam at electroteque.org>
wrote:
On 07/05/2008, at 6:29 AM, Thijs Triemstra | Collab wrote:
> Getting this error when trying to start Red5, latest trunk:
>
> [ERROR] [main] org.red5.server.net.policy.SocketPolicyHandler -
> Exception initializing socket policy server
> java.net.SocketException: Permission denied
> at sun.nio.ch.Net.bind(Native Method)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
> 119)
> at
sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at
> org
> .apache
> .mina
> .transport.socket.nio.SocketAcceptor.registerNew(SocketAcceptor.java:
> 363)
> at org.apache.mina.transport.socket.nio.SocketAcceptor.access
> $800(SocketAcceptor.java:55)
> at org.apache.mina.transport.socket.nio.SocketAcceptor
> $Worker.run(SocketAcceptor.java:222)
> at
> org
> .apache
> .mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51)
> at java.lang.Thread.run(Thread.java:595)
>
> I guess this means red5 now has to be started as root because it
> wants to use port 843? Is it possible to configure this port
> somewhere?
>
Yeh this is what happens when launching from eclipse. With the default
port it needs to be launched as root. Or changed in red5.properties.
_______________________________________________
Red5devs mailing list
Red5devs at osflash.org
http://osflash.org/mailman/listinfo/red5devs_osflash.org
--
It is difficult to free fools from the chains they revere. - Voltaire
Notice - The information in this e-mail is confidential and may be legally privileged. It is intended solely for the recipient(s) named above. If you have received this message in error, or are not a named recipient, please notify the sender immediately at + 1 (604) 685-7619 and please delete this e-mail message from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5devs_osflash.org/attachments/20080509/9a1181d8/attachment-0001.html
More information about the Red5devs
mailing list