Make AEP-121 more generic #337
Open
Conversation
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
rambleraptor
force-pushed
the
121_changes
branch
from
f417614 to
958886e
Compare
toumorokoshi
reviewed
Sep 5, 2025
Comment on lines
-12
to
-15
| Readers might notice similarities between these principles and some principles | ||
| of [REST][]; resource-oriented design borrows many principles from REST, while | ||
| also defining its own patterns where appropriate. | ||
|
|
There was a problem hiding this comment.
I think this is a valid statement, no?
it's helpful to have something to on conceptually - REST is a good concrete example.
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.
AEP-121 has references to RPC APIs. Resource-oriented design isn't different between RPC + REST. I also changed the order, since this should be read first.