@nacx Sorry for my delayed response; this recently became interesting again. I follow that OkHttp allows returning `BufferedSink.outputStream` but I have a problem at the jclouds `HttpRequest` and `HttpResponse` abstraction. My callers generate dynamic content and want to interact with the underlying `OutputStream` which the current system does not provide. I agree that abusing `HttpResponse` for something that is not actually a response is an ugly hack and did something slightly more palatable with `Object`. Reviewing my own code, `EtagOutputStream` was stupid and should be `HttpRequestOutputStream` whose `close` method returns the `HttpResponse`.
-- 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#issuecomment-407926023
