3 ms·
If size is a concern, have your webserver gzip it. https://en.wikipedia.org/wiki/HTTP_compression https://en.wikipedia.org/wiki/HTTP_compression
by robbs 11y ago
If size is a concern, have your webserver gzip it.
https://en.wikipedia.org/wiki/HTTP_compression https://en.wikipedia.org/wiki/HTTP_compression
- lighthawk 11y agoYou should probably have a format that is easily digestible, like WSDL was for SOAP services. Requiring the person serving the RAML to setup their webserver to gzip it and requiring the client to gunzip everything is not very friendly. Having a JSON version of the spec would condense it while still allowing it to be readable, and it would be easily digestible in Javascript and many other languages without an additional parser.
- lotyrin 11y agoWhat server or client toolchains are you using that don't make HTTP Compression trivial and transparent?
- openasocket 11y agoIf you're dead set on using JSON, note that RAML seems to be a subset of YAML, which can be easily converted to JSON. You could do that on the server side, or just use one of the many YAML parsers written in javascript on the client side.