thanks for your quick reply!
The ServerSideModules example was the blueprint for my serverside module - and the communication works perfectly on Wowza2 and all my own Wowza3 test instances. So the error should not be here.
The sequence is generated like this:
Interesting, but also a bit disturbing: The sequence in which the propertis are set is again different from the client side received sequences (both "right" and "wrong"). But as the order in which Wowza sent the property changes was always the same, this did not cause any trouble.
It is read by my eventhandler in my Flex-App
A complete rewrite of my code is only the last option - I am working at university and developing code is not my main task. Therefore I hope that the most efficent way to solve this problem is to find the reason why ONLY ONE server sends the SyncEvents in the wrong sequence instead of creating a workaround that has maybe problems with the next Server/Wowza upgrade.
SO.addEventListener( SyncEvent.SYNC, SOSyncHandler);
It seems, that it is the first time, that you encounted such a problem?
Thanks very much for your thoughts,