java.sql2 DynamicMultiOperation with interlaced exceptions
Douglas Surber
douglas.surber at oracle.com
Mon Oct 16 14:52:11 UTC 2017
I was referring to the reactive stream project. Sorry that wasn’t clear.
Douglas
> On Oct 14, 2017, at 5:30 AM, Viktor Klang <v at lightbend.com> wrote:
>
> Hi Douglas!
>
> >So shoehorning something into the reactive stream model just because you can is against the explicit goals of the project. Per the quote above “backpressure is an integral part of the model”. Using a reactive stream where back pressure is of no value is bad design.
>
> Where are the explicit goals of the project described? I suspect it'd help me greatly to understand those first.
>
> On Fri, Oct 13, 2017 at 9:12 PM, Douglas Surber <douglas.surber at oracle.com <mailto:douglas.surber at oracle.com>> wrote:
> As I said in a previous thread, what would help me is if you explored whether it would be possible to implement the kind of API you are interested in using the proposed API?
>
> Douglas
>
> > On Oct 13, 2017, at 11:56 AM, Lukas Eder <lukas.eder at gmail.com <mailto:lukas.eder at gmail.com>> wrote:
> >
> >
> >
> > 2017-10-13 17:55 GMT+02:00 Douglas Surber <douglas.surber at oracle.com <mailto:douglas.surber at oracle.com> <mailto:douglas.surber at oracle.com <mailto:douglas.surber at oracle.com>>>:
> >
> > So shoehorning something into the reactive stream model just because you can is against the explicit goals of the project. Per the quote above “backpressure is an integral part of the model”. Using a reactive stream where back pressure is of no value is bad design.
> >
> > OK, I tried :) but got it now. Thanks for your detailed responses.
>
>
>
>
> --
> Cheers,
> √
>
> ——————
> Viktor Klang
> Deputy CTO
> Lightbend, Inc.
>
>
More information about the jdbc-spec-discuss
mailing list