This allows clients to write their payloads via an OutputStream
instead of providing an InputStream during construction.  This can
avoid buffering in some situations although one must still provide the
Content-Length.
You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds/pull/1129

-- Commit Summary --

  * JCLOUDS-769: putBlob OutputStream straw man

-- File Changes --

    M core/src/main/java/org/jclouds/http/HttpRequest.java (19)
    M core/src/main/java/org/jclouds/http/HttpResponse.java (19)
    A core/src/main/java/org/jclouds/http/functions/ReturnOutputStream.java (36)
    M 
core/src/main/java/org/jclouds/http/internal/BaseHttpCommandExecutorService.java
 (7)
    M 
core/src/main/java/org/jclouds/http/internal/JavaUrlHttpCommandExecutorService.java
 (38)
    M core/src/main/java/org/jclouds/rest/internal/GeneratedHttpRequest.java (6)
    M core/src/main/java/org/jclouds/rest/internal/RestAnnotationProcessor.java 
(5)
    M core/src/main/java/org/jclouds/rest/internal/TransformerForRequest.java 
(4)
    M 
providers/azureblob/src/main/java/org/jclouds/azureblob/AzureBlobClient.java 
(10)
    M 
providers/azureblob/src/test/java/org/jclouds/azureblob/AzureBlobClientLiveTest.java
 (37)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/1129.patch
https://github.com/jclouds/jclouds/pull/1129.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1129

Reply via email to