-
Notifications
You must be signed in to change notification settings - Fork 467
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.
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
Clarify ingress expiry semantics #5080
base: master
Are you sure you want to change the base?
Conversation
🤖 Here's your preview: https://hhcgk-raaaa-aaaam-abahq-cai.icp0.io |
|
||
The synchronous call endpoint is useful for users as it removes the networking overhead of polling the IC to determine the status of their call. | ||
The synchronous call endpoint is useful for users as it removes the networking overhead of polling the IC to determine the status of their call if a terminal state is reached quickly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure how to best improve it but "reached quickly" is vague, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, but imo it is simply incorrect without it...
An alternative could be the following, wdyt?
The synchronous call endpoint is useful for users as it removes the networking overhead of polling the IC to determine the status of their call if a terminal state is reached quickly. | |
The synchronous call endpoint is useful for users as it reduces the networking overhead of polling the IC to determine the status of their call. |
A request's
ingress_expiry
keeps raising questions.This PR adds clarifications to the different semantics for
call
andread_state
.