Re: [flux-dev] follow up on sync mechanism collaboration

[TAN Sun Seng David <sun.tan@xxxxxxxxx>]

Hi Martin,

> > Server side, Codenvy has a rest api to get the project resources and is using a custom VFS (with ACL) for storage. So I can see 2 options:
> > - run the node server next to the Codenvy main server, the Codenvy main server would work like a Flux client, it will also need to be able to provide resources and request for modified resources.
> > - re implement what we need in Codenvy main server as a Java module, don't use the nodejs server, if it would do nothing else than what i've listed before
> I am not very familiar with the Codenvy structure and API, but I could imagine something like an add-on to Codenvy that acts like a repository (from the flux point of view). This component would need to connect to the Flux websocket messaging channel, listens to the file sync messages, and send out the corresponding file sync messages. This could be something like the MongoDB repo implementation that we have, but instead of using MongoDB to store the resources it uses the Codenvy storage.
> Maybe this could be implemented using the Codenvy rest api. But I am not sure whether it would be possible for this component to be notified when a resource gets changed.
Yes, my team is starting to write a Codenvy repository for Flux, It will 
be written in Java. We will keep you inform on how it goes :)

> > As I didn't find any, i'll write some sequence diagram to explain how the file system sync work, what messages are sent and by who, will share it with you.
> That would be great.
> I also expect the file sync protocol to change in the future (as I said), but we can work on this.
Here is a first draft of the sequence diagram for the file system sync 
part http://sunix.github.io/flux-sequence-diagram/FluxFSSyncSD.svg, you 
can find the source here 
https://github.com/sunix/flux-sequence-diagram/blob/master/FluxFSSyncSD.pic
Any comments are welcome of course.

> > WDYT ?
>
> See my comments above. Would be great to work on this with you guys.
>
> Cheers,
> -Martin
>
>
>
>
>
>
> > Cheers,
> >
> > Sun
> >
> > Le 02/07/2014 18:51, Martin Lippert a écrit :
> > > Hey!
> > >
> > > In the call last week between the Flux team and the Codenvy folks, we discussed a possible collaboration around the basic syncing mechanisms.
> > > The call got recorded and is on YouTube: https://www.youtube.com/watch?v=TJWsawVkpjs, but it is 1h17m long, so be prepared… ;-)
> > >
> > > As discussed I started to document a few general ideas about the architecture of the prototype on the wiki:
> > > https://wiki.eclipse.org/Flux/Prototype
> > >
> > > This page contains a few pointers into the code and explains the general ideas behind the mechanism of the prototype. There are a lot of open questions and things that need to be addressed in the future, but we can start a discussion around that here, if you like.
> > >
> > > Looking forward to working on the more robust and bullet-proof synching mechanism.
> > >
> > > Cheers,
> > > -Martin
> > >
> > >
> > > _______________________________________________
> > > flux-dev mailing list
> > > flux-dev@xxxxxxxxxxx
> > > To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> > > https://dev.eclipse.org/mailman/listinfo/flux-dev
> > _______________________________________________
> > flux-dev mailing list
> > flux-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/flux-dev
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/flux-dev