Saxon:HttpClient

From EXPath

(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
* Use [http://james.apache.org/mime4j/ mime4j] for parsing multipart responses.
* Use [http://james.apache.org/mime4j/ mime4j] for parsing multipart responses.
 +
 +
==Streamability==
 +
 +
Theoretically, the SequenceIterator returned by HttpClient.doSendRequest()
 +
should allow it to be streamable. For instance to not parse the
 +
response content if the user does: http:send-request(...)[1]
 +
(that is, if he/she does not actually access the content).  See
 +
if we can use that...
 +
==Todo==
==Todo==

Revision as of 00:25, 22 January 2010

The implementation of HTTP Client for Saxon.

  • Use Apache HTTP Component (HTTP Core and HTTP Client) series 4 for the HTTP layer.
  • Use mime4j for parsing multipart responses.

Streamability

Theoretically, the SequenceIterator returned by HttpClient.doSendRequest() should allow it to be streamable. For instance to not parse the response content if the user does: http:send-request(...)[1] (that is, if he/she does not actually access the content). See if we can use that...


Todo

  • Adapt to the latest draft.
  • Create a sequence diagram of a simple but complete request, to have a precise idea of the sequence of events (and when the connection can be released, when the response content should have been read, streamibility opportunities, etc.)
Personal tools