expath-cg
expath-cg copied to clipboard
Repository for the W3C EXPath Community Group.
@ChristianGruen, the wiki mentioned the File module as being a Final Report. But this is not the case on the CG homepage . If this is "only" a process thing...
This gives the user much more control over the response parsing, including the ability to choose the parser for the response when they know better than the response's content type....
Here is a summary on the discussion on custom response parsing (#108, #125, and others): In version 1 of the HTTP Client Module, the `override-media-type` was available (inspired by the...
At the moment there is no support for HTTP 1.1 Request Pipelining. This might be a nice thing to think about in future. See for example: https://hc.apache.org/httpcomponents-asyncclient-ga/httpasyncclient/examples/org/apache/http/examples/nio/client/AsyncClientPipelinedStreaming.java
Based on Adam’s suggestion, https://github.com/expath/expath-cg/pull/99#issuecomment-415959322: With a common had implementation core in Java would be beneficial for all implementors of the spec.
The test EXPath-file-writeText3-002 assumes encoding utf-16 is written as big-endian with BOM. It could just as well mean little-endian, each with or without BOM.
The test is bin:unpack-unsigned-integer(xs:base64Binary(xs:hexBinary('ffffffffffffffff')),0,8,'most-significant-first') and the expected result is -1. We are getting the result 18 446 744 073 709 551 615 which seems correct to me.
So er... I can't seem to find the spec for the HTTP 1.0 client in this repo? Anyone know where it is?
I think we need better controls over Request body serialization. Some concerns I have: > xs:base64Binary, xs:hexBinary > Value will be sent as binary data, the media type will be...
We need a test suite for HTTP Client 2.0. For example, at the moment I want to make sure we can handle the various XDM HTTP JSON request/responses that we...