expect so they would always be preferred over
Akka.
Thanks,
Shawn
On Monday, May 25, 2015 at 4:53:58 AM UTC-5, √ wrote:
Hi Shawn,
The use case you're referring to (transitive ordering) I think
traditionally is accomplished in the actor model with the use of
arbiters:
https
on these aynch semantics because he want's it to
behave like an asynch queue of ActiveMQ and feels Akka should provide
something like that out of the box.
I told him I don't think so but you get all the tools to build it yourself
whatever semantics you want.
Thanks,
Shawn
--
Read the docs: http
Patrik, would you kindly elaborate on why akka-sbt-plugin was retired?
sbt-native-packager is more general and powerful but I don't recall it
having anything built-in to support Akka.
So, prior to 2.3.x we had an relatively easy and documented way for a
*newbie* to deploy an Akka app with the
I'd like to hear more on this as well. Searching the documentation for
2.3.5 doesn't even discuss deployment in any detail.
I recognize that sbt-native-packager is cool, but for an later version of
Akka to have *less documentation* on how to deploy than the previous
version is rather sad,
Konrad, I don't see how simply linking to sbt-native-packager helps with
the original question.
As I mentioned, sbt-native-packager has nothing akka specific about it,
whereas akka-sbt-plugin was akka-aware and *did* akka-specific things.
What the documentation needs is an example built.sbt or
