chore(doc): add initial readme for jade-service-runner #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shanejonas
reviewed
Apr 25, 2019
Co-Authored-By: zcstarr <zcstarr@gmail.com>
BelfordZ
approved these changes
Apr 27, 2019
BelfordZ
suggested changes
Apr 27, 2019
README.md
Outdated
| Running and accessing JSON-RPC services is currently difficult. JSON-RPC services are a defacto standard for communicating with decentralized services. Developers need to perform one or more of the following tasks | ||
| to ensure their dApps has access to the services it needs to run. | ||
| - embed the service directly in the App | ||
| - approach can potentially suffer from bloat, if the service takes alot of resources to run |
There was a problem hiding this comment.
Suggested change
| - approach can potentially suffer from bloat, if the service takes alot of resources to run | |
| - approach can potentially suffer from bloat, if the service takes alot of resources to run |
README.md
Outdated
| - embed the service directly in the App | ||
| - approach can potentially suffer from bloat, if the service takes alot of resources to run | ||
| - use a remote centralized node (CryptoKitties) | ||
| - this route leads to some centralization in, the sense that traffic has to flow through a centralized point |
There was a problem hiding this comment.
Suggested change
| - this route leads to some centralization in, the sense that traffic has to flow through a centralized point | |
| - this route leads to some centralization in, the sense that traffic has to flow through a centralized point |
README.md
Outdated
| - use a remote centralized node (CryptoKitties) | ||
| - this route leads to some centralization in, the sense that traffic has to flow through a centralized point | ||
| - rely on the user to have the service configured and running ambiently | ||
| - this approach is the most difficult for, the end user, as it requires setup from the end user's perspective |
There was a problem hiding this comment.
Suggested change
| - this approach is the most difficult for, the end user, as it requires setup from the end user's perspective | |
| - this approach is the most difficult for, the end user, as it requires setup from the end user's perspective |
Co-Authored-By: zcstarr <zcstarr@gmail.com>
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Its a definite WIP atm, just figured I'd file this as well as the issue #2 .