jakartaee / rest

Jakarta RESTful Web Services
Other
362 stars 117 forks source link

Support for EXI and FastInfoset #41

Open glassfishrobot opened 13 years ago

glassfishrobot commented 13 years ago

Transmission of XML is quite a burden for the net due to a lot of formatting and readability information. Due to that, several proposals had been created, like Fast Infoset. It makes sense to support such transport encodings. As client and server only rely on the transported encoding, it is necessary to contain the used encoding in the specification of the service. As the service is implemented using JAX-RS with transparency to the underlying levels like Servlets or Containers, JAX-RS must contain a possibility to define the encoding supported by the service (otherwise the service implementation would become dependent of specific Servlets or Containers).

I want to propose a minimum set of encodings:

(Mandatory) EXI - http://www.w3.org/TR/2011/PR-exi-20110120/

(Optional but mentioned) Fast Infoset

Affected Versions

[2.0]

glassfishrobot commented 6 years ago
glassfishrobot commented 13 years ago

@glassfishrobot Commented Reported by mkarg

glassfishrobot commented 12 years ago

@glassfishrobot Commented @mpotociar said: Out of scope for 2.0 and very limited time left - deferring to a future release.

glassfishrobot commented 9 years ago

@glassfishrobot Commented @spericas said: Given the growth of JSON in recent years. Is support for binary XML formats still as relevant as before? Perhaps this is an area for the JAX-RS implementations to innovate, not the spec.

glassfishrobot commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA JAX_RS_SPEC-36