在 2014年4月27日星期日UTC+8上午2时15分31秒，Justin du coeur写道： > > On Fri, Apr 25, 2014 at 4:00 PM, 杨博 <[email protected] <javascript:>>wrote: > >> Does this project interest you or scare you? >> > > Somewhere in-between, I'd say -- I'm intrigued but cautious. The concept > is *quite* interesting, and for some state machines I can imagine it being > enormously useful. That said, while it's obvious how it works for a single > entry point, I'm not clear on how it would work with one of my typical > Actors, which often respond quite differently to half a dozen different > messages. If this is so deeply become-based, it *sounds* like it might > have problems when those are interleaved. > I guess I won't resolve this problem at any time. Yes, I can resolve it by dispatching different message to different Futures in one actor. But IMHO, it's not the best design model with Akka. I suggest you forward different messages to different actors, and use Future in those actors.
> But the generated code is so voluminous, I can't quickly figure out if > that's true. (The bulk of the generated code is a mild concern as well, > although not a dramatic one if the size of the generated code is roughly > linear with the original.) > > How well does the Future mechanism play with more heterogeneous Actors, > with a bunch of different entry points? > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
