triggers get responded right away (202) with an activation is and then sent to the queue to be processed async same as async action invokes.
I think we would keep same contract as today for this type of activations that are eventually process different from blocking invokes including we Actions were the http client hold a connection waiting for the result back. - Carlos Santana @csantanapr > On Aug 17, 2018, at 6:14 PM, Tyson Norris <tnor...@adobe.com.INVALID> wrote: > > Hi - > Separate thread regarding the proposal: what is considered for routing > activations as overload and destined for kafka? > > In general, if kafka is not on the blocking activation path, why would it be > used at all, if the timeouts and processing expectations of blocking and > non-blocking are the same? > > One case I can imagine: triggers + non-blocking invokes, but only in the case > where those have some different timeout characteristics. e.g. if a trigger > fires an action, is there any case where the activation should be buffered to > kafka if it will timeout same as a blocking activation? > > Sorry if I’m missing something obvious. > > Thanks > Tyson > >
