Hi Sergey,
Flow.Subscription is going away. That part of the API is a sample of how
things will look like when 2.1 is released - we will remove as much as
possible from Flow.*. If there is something which cannot be removed
(like Subscription), we'll consider the usecase (SSE in this case) and
copy it into JAX-RS somehow (SseSubscription).
I know that it feels odd (and it is) to have this done on part of the
API and not on another part, but it was part of the internal review
process and my arguments were ignored..
Is this clearer now?
Thanks and regards,
Pavel
On 15/02/2017 22:17, Sergey Beryozkin wrote:
> Hi Pavel
>
> The question from my colleague Andriy (more to come)
>
> Can you clarify why both Flow.Subscription and SseSubscription are
> both used interchangeably ?
>
> Thanks, Sergey
>
> On 15/02/17 15:47, Pavel Bucek wrote:
>> Dear experts,
>>
>> if you have any feedback for SSE, please provide it by the end of
>> this week, sooner the better.
>>
>> (it doesn't mean that feedback received afterwards won't be
>> evaluated; it's mainly about keeping the ball rolling).
>>
>> Also, I'd like to announce that Early Draft Review will be started
>> shortly afterwards. I believe we reached the point when we can say
>> that we have done some progress and we could use feedback from wider
>> group. EDR will hopefully help with that.
>>
>> Thanks and regards,
>> Pavel
>>
>