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

Method for client to determine which payload formats are supported #10

Open
achimr opened this issue Sep 19, 2014 · 0 comments
Open

Method for client to determine which payload formats are supported #10

achimr opened this issue Sep 19, 2014 · 0 comments
Assignees

Comments

@achimr
Copy link
Contributor

achimr commented Sep 19, 2014

-- It seems there is no way for the caller to know what kind of payload the provider can process. While it can likely be handled through error reporting, it'd be better to be able to query the capabilities of the provide before sending data. (reported by Yves Savourel)

HTTP already has content negotiation but it does not apply, it defines the flexible delivery of different content formats from server to client: http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html; we need another function that queries the provider for acceptable translation request formats

@achimr achimr self-assigned this Sep 19, 2014
@achimr achimr added this to the v2.0 Specification Issues milestone Sep 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant