Hi Maxim, thanks for sharing that. From my point of view we made the right decision to implement our own clustering. At least until the other solution is ready.
I had made some test with our clustering that went well. However the synchronizing of the recordings from the slave to the master is still a todo. I had implemented different variants for that, but they all had some kind of backdraw. I will summarize that in another mail when I have synced and updated to the latest revision and can prepare some use cases. Sebastian 2013/1/13 Maxim Solodovnik <[email protected]> > ---------- Forwarded message ---------- > From: <[email protected]> > Date: Jan 12, 2013 10:41 PM > Subject: 2 issues changed in red5 > To: <[email protected]> > Cc: > > Updates: > Status: > Owner: > > Comment by mondain: > Clustering is being rearchitected and the older versions are no longer > supported for a number of reasons. The Cluster feature will be provided as > a Red5 plugin once the work is completed. The source will be located here: > http://red5.googlecode.com/**svn/java/plugins/trunk/cluster<http://red5.googlecode.com/svn/java/plugins/trunk/cluster> > > Affected issues: > issue 3: Clustering Way and Test > > http://code.google.com/p/red5/**issues/detail?id=3<http://code.google.com/p/red5/issues/detail?id=3> > > issue 185: The Cluster problem on higher version Red5 > > http://code.google.com/p/red5/**issues/detail?id=185<http://code.google.com/p/red5/issues/detail?id=185> > > > > -- > You received this message because you are listed in the owner > or CC fields of these issues, or because you starred them. > You may adjust your issue notification preferences at: > http://code.google.com/**hosting/settings<http://code.google.com/hosting/settings> > > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
