@phelps-sg, @bherd-rb (also @EconomicSL/core-devs ) I am considering adding Akka as a dependency for esl-auctions. Akka is being heavily used in both the auctions-simulation-example and auctions-remote-example projects and there is now a lot of duplicate code in both those repos that I would prefer to push up into the esl-auctions core.
I will however be sure to isolate the use of Akka to it own package within esl-auctions as it is possible to run auction simulations using the esl-auctions API without Akka and I do not want to force users to make use of Akka if they don't want to.
Am closing this because we have added Akka as a dependency (but we have encapsulated all code touching akka into an actors package which would allow us to have it be a separate library).
@phelps-sg, @bherd-rb (also @EconomicSL/core-devs ) I am considering adding Akka as a dependency for
esl-auctions
. Akka is being heavily used in both the auctions-simulation-example and auctions-remote-example projects and there is now a lot of duplicate code in both those repos that I would prefer to push up into theesl-auctions
core.I will however be sure to isolate the use of Akka to it own package within
esl-auctions
as it is possible to run auction simulations using theesl-auctions
API without Akka and I do not want to force users to make use of Akka if they don't want to.Thoughts?