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.

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

Get rid of the mode key. In all cases the server decides whether to #174

Closed
wants to merge 3 commits into from

Conversation

pvretano
Copy link
Contributor

execute a process synchronously or asynchronously. The client, however,
can provide hints via the Prefer HTTP header defined in RFC 7240.

execute a process synchronously or asynchronously.  The client, however,
can provide hints via the `Prefer` HTTP header defined in RFC 7240.
@bpross-52n bpross-52n linked an issue Apr 19, 2021 that may be closed by this pull request
@jerstlouis
Copy link
Member

jerstlouis commented Apr 19, 2021

One suggestion was a query parameter for a client to force a particular mode, as opposed to simply indicating a preference, e.g. respond=sync or respond=async.

One of the advantage of that is that the same execute request (not hard-coding mode) could be used with either a query parameter or with the Prefer header (much like the f= query parameter being able to override the Accept header).

into a opaque URI that might, for example, be embeded in a web page.
@bpross-52n
Copy link
Contributor

Closed by SWG decision (details will follow)

@bpross-52n bpross-52n closed this May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants