Open mDuo13 opened 3 years ago
an algorithm that synchronizes the information, in real time.
tx_history
example responses to an includeaccount_objects
example responses to an includeFor purposes of this ticket, splitting sections into their own pages is sufficient; they don't need to be updated, made interactive, etc. (That would be good, but doing it for all the stuff that needs to be broken up would make this too large a task to finish and review in a timely fashion, so updating the content should be separate tasks.) Also, splitting up the payment channels doc is to be done in #1055.
Some pages are too large, making it easy to get lost, hard to find what you want, or just causing them to load slowly.
The following is a list of candidates for potentially splitting into smaller, individually-functional pieces. They don't all necessarily need to be split up; this is just a starting point for making careful decisions about what to keep together or divide:
also, the RippleAPI/ripple-lib reference, but that's sourced from outside this repo.