ShareObject: no sync event on client after attribute changed if value is of type Object about red5-server HOT 1 CLOSED

This should be resolved with the commit on red5-server-common The addition of setDirty(boolean) is meant to be used to indicate a modification made to a custom object and force an update. The simple addition of "equals" will not work and modifications directly on the referenced object do not trigger a "property" change so the object appears to be unmodified to the server. So in summary, make sure you call setDirty(true) before you call setAttribute when you've modified the SharedObject attribute directly on the server; your updated example code may be found here: https://github.com/Red5/red5-issues/blob/master/src/main/java/org/red5/issues/issue46/Application.java

from red5-server.