It really depends on the imp. One simple way is to bundle all the batched invocations in the same invocation message, in which case it can be sent by any available thread in a client.
We can also put two invocations across more than one invocation message in client but it requires further ordering of the received invocation messages in server. The key point is the requirement of the ordering of the invocations that are involed in a batch. Pseudo codes may look like this: Client side Batchcall bc = new Batchcall: batchcall.add(f1); Batchcall.add(f2); Batchcall.send() In Server side. The ordering of invocation must be f1 then f2 regardless of whichever thread is executing the invocation. Regards, Thanks. On Sun, 13 Jan 2019 at 12:07 pm, yizhenqiang <[email protected]<mailto:[email protected]>> wrote: Then I have a problem, since the consumer side can send messages of the same batch number in multiple threads, then what is the meaning of guaranteeing the same thread consumption on the provider side? Can you give a scene? 那我有个问题，既然consumer端可以多线程发送同一批次号的消息，那么在provider端保证同一线程消费的意义在哪里？能举个场景吗？ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/apache/incubator-dubbo/issues/3215#issuecomment-453793466>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKFrGeJ5zlm-2iVG5QRf4xxMXVXlT9nBks5vCobGgaJpZM4Z85nt>. [ Full content available at: https://github.com/apache/incubator-dubbo/issues/3215 ] This message was relayed via gitbox.apache.org for [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
