search

rlalfo / google-http-java-client

Automatically exported from code.google.com/p/google-http-java-client
0 stars 0 forks source link

UrlFetchTransport optimization since we know content is byte[] #218

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
External references, such as a standards document, or specification?

http://javadoc.google-http-java-client.googlecode.com/hg/1.14.1-beta/com/google/
api/client/extensions/appengine/http/UrlFetchTransport.html

https://developers.google.com/appengine/docs/java/javadoc/com/google/appengine/a
pi/urlfetch/HTTPResponse#getContent()

https://developers.google.com/appengine/docs/java/javadoc/com/google/appengine/a
pi/urlfetch/HTTPRequest#setPayload(byte[])

Java environments (e.g. Java 6, Android 2.3, App Engine, or All)?

App Engine

Please describe the feature requested.

We design StreamingContent on the idea of a writeTo(OutputStream) method and 
HttpResponse.getContent() that returns an InputStream.  However, there are 
quite a few cases where we have a byte[] that we set as the content that is 
then unnecessarily copied into another byte[] just for the sake of the 
implementation of the HTTPRequest.setPayload().  We need some way of designing 
the HTTP request/response system so it can more efficiently handle this case.

Original issue reported on code.google.com by yan...@google.com on 22 Apr 2013 at 9:51