thought about
>>>> some kind of following flow:
>>>> frontend -> queue -> flink -> redis(pub/sub)<- frontend
>>>>
>>>> I.e. I have two major use cases - async aggregated analytics/stats
>>>> computing
>>>> and "syn
might be node/play or
>>> any
>>> other technology that won't have a problem of "waiting" for the
>>> response, so
>>> the only question - how to implement this feedback ?
>>> Might be some kind of Sink?
>>>
>>> Any ideas would be appreciated,
>>> Igor
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-event-processing-immediate-feedback-tp5978.html
>>> Sent from the Apache Flink User Mailing List archive. mailing list
>>> archive at Nabble.com.
>>>
>>
>
uot;waiting" for the response,
>> so
>> the only question - how to implement this feedback ?
>> Might be some kind of Sink?
>>
>> Any ideas would be appreciated,
>> Igor
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-event-processing-immediate-feedback-tp5978.html
>> Sent from the Apache Flink User Mailing List archive. mailing list
>> archive at Nabble.com.
>>
>
s feedback ?
> Might be some kind of Sink?
>
> Any ideas would be appreciated,
> Igor
>
>
>
>
> --
> View this message in context:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-event-processing-immediate-feedback-tp5978.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive
> at Nabble.com.
>
xt:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-event-processing-immediate-feedback-tp5978.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at
Nabble.com.
