If it's anything like in *Lagoa* http://home.lagoa.com/ then the scene is up-to-date at all times on the browser, but more importantly, the server. The server sends the latest state at first open then streams little changes asynchronously as they happen.
Think of it like a chatroom where when you enter the room you're given the chatlog of all conversation up to that point, and then you watch things happen. It's pretty similar. On Wed, Jul 10, 2013 at 9:29 AM, Marc-Andre Carbonneau < [email protected]> wrote: > >>What I really like is the collaborative potential - working on the same > scene with others simultaneously can be an interesting design tool. > > I understand the power but I wonder how they solve the problem, how does > it work? I guess it's some sort of referencing pipeline where you can put a > model local inside the scene, modify it and save. While the other person > only sees the reference up to when you decide to publish a new version? > > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Stefan Kubicek > Sent: 10 juillet 2013 07:30 > To: [email protected] > Subject: Re: clara.io > > +1 on pretty much all arguments about privacy - especially some > +advertising agencies > can be totally anal about security, they are almost bound to disallow > cloud-based storage of data. > The same probably goes for film work. Allowing installation on a dedicated > server for total user control would be a big plus here. > > As for problems with low internet bandwidth in certain locations, I think > this is where time is working for them. > > What I really like is the collaborative potential - working on the same > scene with others simultaneously can be an interesting design tool. > > >
