RFR: 8087112: HTTP API and HTTP/1.1 implementation

[Simone Bordet]

Failed to proof-read.

I meant "there is *no* timeout for async calls either" below.

Thanks !

On Mon, Sep 28, 2015 at 3:08 PM, Simone Bordet <simone.bordet at gmail.com> wrote:
> Hi,
>
> On Mon, Sep 28, 2015 at 2:50 PM, Michael McMahon
> <michael.x.mcmahon at oracle.com> wrote:
>> We might reconsider this. Currently there is no timeout for blocking
>> calls, which I guess is problematic.
>
> Just to be 100% clear on this, there is timeout for async calls
> either. The only option is to *block* via CF.get(time), which is of
> course against an async API and therefore not a viable solution.
>
> --
> Simone Bordet
> http://bordet.blogspot.com
> ---
> Finally, no matter how good the architecture and design are,
> to deliver bug-free software with optimal performance and reliability,
> the implementation technique must be flawless.   Victoria Livschitz



-- 
Simone Bordet
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz