Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move to react #1

Open
buildog opened this issue Sep 11, 2017 · 4 comments
Open

move to react #1

buildog opened this issue Sep 11, 2017 · 4 comments
Assignees

Comments

@buildog
Copy link

buildog commented Sep 11, 2017

The idea is to extract the renderer of https://github.com/livepeer/LivepeerDesktop (after Emitter stuff will be ready)

So we will have something like:
livepeer-emitter (shared lib/api)
livepeer-gateway (renderer)
livepeer-desktop (electron) + (renderer, aka gateway) + (emitter)

sound good @ericxtang @dob ?

@buildog buildog self-assigned this Sep 11, 2017
@buildog
Copy link
Author

buildog commented Sep 11, 2017

cf. livepeer/go-livepeer#94

@dob
Copy link
Member

dob commented Sep 11, 2017 via email

@ericxtang
Copy link
Member

@buildog we are working on some interface updates on the Livepeer node, so the interface may undergo some changes. Want to make sure this doesn't affect your development too much. I think I'll have a PR and update the doc in the next 2-3 weeks. My goal is to have a readthedocs site that documents the endpoints to the node, similar to the raiden docs.

Want to make sure I understand the benefit of extracting these 3 modules. Are we basically importing the emitter into livepeer-desktop after this? And this means other Node.js apps can import the emitter or the renderer to interact with Livepeer?

@buildog
Copy link
Author

buildog commented Sep 11, 2017

awesome for the doc @ericxtang!

and yes, it's exactly what it is about, it's split concerns so projets have re-usable and stable components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants