You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to add some other data along with SharedObjectScope. For that I want to extend it in my custom class in red5 application and create object of custom classs say MySOScope when SharedObjectService#createSharedObject() is called.
As of now, instance of SharedObjectScope is directly created here, but can I change code in way:
SharedObjectScope will not be created directly.
Its mapping will be in red5-default.xml. By reading, beans id & class, instance for SharedObjectScope will be created.
Then further if I want to implement any custom class in my application, I can extend SharedObjectScope in MySOScope, and override that beans id and class with reference to MySOScope as value of class attribute.
Then it should be able to create instance of MySOScope instead of SharedObjectScope.
Are there any cons in these modifications? Please help me to see wide picture if I am implementing these modifications.
The text was updated successfully, but these errors were encountered:
Hi,
I want to add some other data along with
SharedObjectScope
. For that I want to extend it in my custom class in red5 application and create object of custom classs sayMySOScope
whenSharedObjectService#createSharedObject()
is called.As of now, instance of
SharedObjectScope
is directly created here, but can I change code in way:SharedObjectScope
will not be created directly.SharedObjectScope
will be created.SharedObjectScope
inMySOScope
, and override that beans id and class with reference toMySOScope
as value of class attribute.MySOScope
instead ofSharedObjectScope
.Are there any cons in these modifications? Please help me to see wide picture if I am implementing these modifications.
The text was updated successfully, but these errors were encountered: