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

DOCS & FAQ: Architecture #38

Open
tiblu opened this issue Nov 17, 2015 · 0 comments
Open

DOCS & FAQ: Architecture #38

tiblu opened this issue Nov 17, 2015 · 0 comments

Comments

@tiblu
Copy link

tiblu commented Nov 17, 2015

First of all - thanks a lot for open sourcing Hackpad.

It would be nice if someone with deep insight would contribute architectural documentation of the Hackpad in the Wiki. Most of the questions I get when browsing the source are probably actually related to the AppJet engine, but the info is hard to find.

It would be nice if it answered following questions:

  • What components (libraries, technologies...) are involved and how they talk to each other?
  • How to extend the functionality? The in depth view how "task list" functionality comes together with all the FE and BE parts.
  • Architectural decisions:
    • Why is Hackpad built on top of Etherpad not for example Etherpad Lite? It might be as easy, as Etherpad Lite did not exists at the time. The problem with building on top of Etherpad which is on top of AppJet, which open source development seems to be discontinued and there are no resources available.
    • Is there any edge in using AppJet to plain (Node).JS solution like Etherpad Lite? From what I see AppJet is Java/Scala framework that runs the JavaScript code inside JVM using Rhino engine. Seems like a very fat stack. What are the benefits of the stack? More of a AppJet engine question, but the info is very hard to find.

If this should be discussed somewhere else, please let me know.

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

No branches or pull requests

1 participant