Red5.getConnectionLocal().getScope() returns null after HTTP call

[andreslorek]

I'm using Red5-1.0.4 and having an issue with Red5.getConnectionLocal().getScope(). I work with an external system, operating with an API.

In some methods, I need to make something like this:

Red5.getConnectionLocal().getScope(); // returns the correct Scope
// Do some call to an API via HTTP
Red5.getConnectionLocal().getScope(); // sometimes returns the correct Scope and some others returns null

As a workaround, I'm saving the result of the .getScope() method before the API call, so I can use it after that without any problem.

[mondain]

Why would the ThreadLocal value in Red5 change due to your API call? The only way I see this happening is if you are somehow modifying it or your in a method where you are not maintaining access to the connection instance.

[mondain]

This could possibly be related to issue #39 if you're using a pre 1.0.5 version.