-
Notifications
You must be signed in to change notification settings - Fork 10
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
Feature Request: Add ability to get server capability #45
Comments
I'll have this added for the next release. |
I am curious about what this would be used for. If you are adding custom |
My main objective was trying to think of a simple way to do a sanity check (ring the door bell). i.e. make small request to see if I have the right address. this seemed like a convenient way that returns something small, but didn't exist in the client. It seems like it would be very useful if I wanted to add a compressed output format, and be able to check if it's available? I found hapi yesterday, so it is still new to me. |
Thanks. I'll raise this issue with the standards group. It would be useful to have a standard way of doing this. |
A full year has elapsed on this ... there has been some progress but probably you have worked around it already. |
Regarding compression, I've always relied on HTTP encoding, where you can let the server (apache for example) transmit the data compressed. See for example https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding . |
For compression, I would try what @jbfaden discussed earlier. We don't have a compressed format because the HTTP spec already solves the problem. The server just needs to be configured to send compressed data over the wire. Most client libraries will transparently decompress. Currently, the |
e.g.
The text was updated successfully, but these errors were encountered: