Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix a broken link in doc #784

Open
wants to merge 1 commit into
base: gh-pages-source
Choose a base branch
from
Open

Fix a broken link in doc #784

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/guide_restli_server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -295,7 +295,7 @@ implement asynchronous Rest.li resources. The templates are:
- `SimpleResourceTaskTemplate`

The Rest.li server will automatically start any `Task` that is returned
by a `Task` based method by running it through a ParSeq engine. This ParSeq engine is launched while the Rest.Li server is launched ([for example, NettyStandaloneLauncher](https://github.com/linkedin/rest.li/blob/master/restli-netty-standalone/src/main/java/com/linkedin/restli/server/NettyStandaloneLauncher.java#L84)), so the user does not run these task using another engine explicitly, instead, Rest.Li framework will the run the method's returning `Task` using the ParSeq engine when the method is invoked. (For details check [RestLiMethodInvoker.java](https://github.com/linkedin/rest.li/blob/master/restli-server/src/main/java/com/linkedin/restli/internal/server/RestLiMethodInvoker.java)). Also refer to [this document page](./Asynchronous-Servers-and-Clients-in-Rest_li.md) regarding the best practice of writing asynchronous client and service logic. `Callback`-based methods do not receive special treatment.
by a `Task` based method by running it through a ParSeq engine. This ParSeq engine is launched while the Rest.Li server is launched ([for example, NettyStandaloneLauncher](https://github.com/linkedin/rest.li/blob/master/restli-netty-standalone/src/main/java/com/linkedin/restli/server/NettyStandaloneLauncher.java#L84)), so the user does not run these task using another engine explicitly, instead, Rest.Li framework will the run the method's returning `Task` using the ParSeq engine when the method is invoked. (For details check [RestLiMethodInvoker.java](https://github.com/linkedin/rest.li/blob/master/restli-server/src/main/java/com/linkedin/restli/internal/server/RestLiMethodInvoker.java)). Also refer to [this document page](/rest.li/Asynchronous-Servers-and-Clients-in-Rest_li) regarding the best practice of writing asynchronous client and service logic. `Callback`-based methods do not receive special treatment.

## Sub-Resources

Expand Down