[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [flux-dev] follow up on sync mechanism collaboration
|
Hi All,
I just had some time to rework/think about a potential sync mechanism
for Codeny/Eclipse Che (not Flare anymore afaik).
So I've tested the flux demo, checking out the prototype and tested the
file sync and the node.js server. It works really well ! wow :) I'm
impressed
So I'm very excited to use in with Codenvy, for file system sync and
maybe more in the future ! I've also listen to the pod cast on se-radio,
I liked it.
So our first step would be, starting from the prototype, write a simple
CLI command that would run a sync process on the file system and
synchronize against a workspace/or a project in Codenvy.
We would like to write a first implementation with flux and codenvy, I
was wondering what was the node server doing ?
From my understanding,
- it hosts the Orion editor + the simple browser resource navigator
- it serves the project resources, and act like a Flux client. If
any message requesting a resource, it would managed to reply with the
right file attached.
- it serves the websocket "server" localhost:3000
- it keeps the project files + metadata (timestamp, etc ...) in a
MongoDB
Am I right ?
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
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.
WDYT ?
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
