Repository navigation
Exchange: rewrite the docs from FORA Server and add them to the sidebar - #85
Open
EugeneDymo wants to merge 2 commits into
Open
EugeneDymo wants to merge 2 commits into
EugeneDymo wants to merge 2 commits into
Conversation
The eight Exchange pages described an earlier design rather than FORA Server: DynamoDB, ClickHouse, a WAL, a config file, hot reload, gRPC health, per-tenant keys and latency targets. They were also off the sidebar. The overview now follows one resource through FORA Server's Exchange: how a catalog push is accepted, how offers are selected and signed, how a purchase is charged and recorded, what the usage report rules are, how an agent opens an account, how each request is verified, and what an operator runs. The billing page is now Billing and Ledgers. It states the real adapter contract, the three ledgers, currencies, identifiers, the charging flow, free and subscription items, fees and publisher revenue, and failure handling. Request Flows, Configuration, Storage Model, Multi-Tenant, Scaling and Health Checks are retired, and their URLs redirect to the overview. The sidebar has an Exchange group with Overview and Billing and Ledgers. FORA for Exchange Operators is corrected against the same code, and notes where FORA Server's Exchange does not follow a protocol rule.
…ws page TestDocHandlerExampleCompiles pinned the DiscoverResources handler example of the Exchange request-flows page to conformance/docgo/requestflows. The page is retired and redirects to the Exchange overview, so the test had no page to read and failed. The example went with the page: it showed a handler design against stubs, not FORA Server's handler. Remove the test, the package it generated, and the comment that mentioned the example.
This branch has not been deployed
This file contains hidden or 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
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.
The eight Exchange pages described an earlier design rather than FORA Server: DynamoDB, ClickHouse, a WAL, a config file, hot reload, gRPC health, per-tenant keys and latency targets. They were also off the sidebar.
The overview now follows one resource through FORA Server's Exchange: how a catalog push is accepted, how offers are selected and signed, how a purchase is charged and recorded, what the usage report rules are, how an agent opens an account, how each request is verified, and what an operator runs. The billing page is now Billing and Ledgers. It states the real adapter contract, the three ledgers, currencies, identifiers, the charging flow, free and subscription items, fees and publisher revenue, and failure handling.
Request Flows, Configuration, Storage Model, Multi-Tenant, Scaling and Health Checks are retired, and their URLs redirect to the overview. The sidebar has an Exchange group with Overview and Billing and Ledgers.
FORA for Exchange Operators is corrected against the same code, and notes where FORA Server's Exchange does not follow a protocol rule.