Hi, On 15 Aug, 2012, at 3:41, Carsten Neumann <carsten_neum...@gmx.net> wrote:
> Hello Volker, > > On 08/14/2012 11:16 AM, Volker Settgast wrote: >> concerning the skinning-with-cluster problem: >> >> > > > > Thinking some more about this, even if the call to > data->setDataValid(false) never happens the servers should still get > updated data. However, if your application calls > OSG::commitChangesAndClear() after rendering, all changes that were done > as part of rendering are lost - the only safe time to clear the > changelist is immediately after transmitting it, but the ClusterWindow > lumps the transmit together with rendering so that it is difficult for > the app to clear the CL at the right time. > It seems ClusterWindow should have an option (default: true) that > controls if it clears the changelist after transmitting it. small comment, changes during local rendering should never be needed to get the clustering right. Usually they should not even be transmitted. Because, rendering locally on the master while clustering is optional, for example on our main cluster the application is started remotely, without anybody being even being logged into the master, so no rendering will happen in this setup. kind regards gerrit ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
