ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-20 11:45:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

[DOC] rippled intro added for better navigation

Browse Source
This commit is contained in:
mDuo13
2014-11-20 16:46:43 -08:00
parent a23c0927f5
commit 86a58d4033
2 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
content/websocket_api.md → content/rippled.md
View File

@@ -1,3 +1,12 @@
# rippled #
The core peer-to-peer server that operates the Ripple Network is called `rippled`. Each `rippled` server connects to the Ripple Network, relays cryptographically signed transactions, and maintains a local copy of the complete shared global ledger. The source code for `rippled` is written in C++, and is [available on GitHub under an open-source license](https://github.com/ripple/rippled).
* [Building and Installating](https://wiki.ripple.com/Rippled_build_instructions)
* [API Reference](#api-methods)
* [Transaction Reference](transactions.html)
* Client Library - [Javascript](https://github.com/ripple/ripple-lib)
# WebSocket and JSON-RPC APIs # # WebSocket and JSON-RPC APIs #
If you want to communicate directly with the `rippled` server, you can use either the WebSocket API or the JSON-RPC API. Both APIs use the same list of commands, with almost entirely the same parameters in each command. Whereas the [Ripple-REST API](ripple-rest.html) provides a simplified interface on top of the WebSocket API for easier integration, these APIs provide the full power of Ripple but require slightly more complexity: If you want to communicate directly with the `rippled` server, you can use either the WebSocket API or the JSON-RPC API. Both APIs use the same list of commands, with almost entirely the same parameters in each command. Whereas the [Ripple-REST API](ripple-rest.html) provides a simplified interface on top of the WebSocket API for easier integration, these APIs provide the full power of Ripple but require slightly more complexity:

4
rippled-apis.html
View File

@@ -5,7 +5,7 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta name="viewport" content="width=device-width"> <meta name="viewport" content="width=device-width">
<title>Ripple Developer Portal: rippled APIs</title> <title>Ripple Developer Portal: rippled</title>
<!-- favicon --> <!-- favicon -->
<link rel="icon" href="favicon.ico" type="image/x-icon"> <link rel="icon" href="favicon.ico" type="image/x-icon">
@@ -72,7 +72,7 @@ mixpanel.init("132d42885e094171f34467fc54da6fab");
$(".flatdoc-content").empty(); $(".flatdoc-content").empty();
$(".content-root .menubar .menu").empty(); $(".content-root .menubar .menu").empty();
Flatdoc.run({ Flatdoc.run({
fetcher: Flatdoc.file('content/websocket_api.md') fetcher: Flatdoc.file('content/rippled.md')
}); });
$(document).on('flatdoc:ready', function() { $(document).on('flatdoc:ready', function() {
$().multicode_tabs(); $().multicode_tabs();