2013/10/21 FUJITA Tomonori <[email protected]>
> On Sat, 12 Oct 2013 20:04:35 +0900
> Satoshi Kobayashi <[email protected]> wrote:
>
> > I noticed that an event between modules may get confused in multithread.
> It
> > is the following scenarios.
> >
> > 1. The module A sends an event to the module B
> > 2. The module B requires time to process the event...
> > 3. The module A sends an event to the module C
> > 4. The module C returns an answer soon
> > 5. The module A is misunderstanding that It is the response from the
> module
> > B (in fact the module C)
> >
> > I wrote PoC reproducing this issue as follows.
>
> Yeah, you need a trick like using request ids to do such. We have been
> thinking about the better way for component communication (such as
> JSON RPC, Message Pack RPC, etc). Also it could be used for
> communication with non Ryu software.
>
Could you tell me about the trick? I am very glad if there is a code or
point.
I think that it is kind, if the trick is contained in Ryu (not application).
> Any proposals?
>
I do not have a specific proposal now.
However, I want
1. The backend is concealed from a user (developer)
- I do not want to consider in programming (exclude debugging) whether
the backend is JSON-RPC, MessagePack, AMQP, HTTP, etc…
2. Intelligibility > Performance
- This should agree also in Ryu-way and my liking
Thanks,
Satoshi
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel
