For the current Chunker if the upstream sends larger messages than the
chunk size the buffer can slowly fill up until the app OOMs. Change it
so it only pulls if the buffer is empty
* Basic working java api
* Most of the compile only spec in java
* Bits and bobs
* Abstract class for java dsl
* Move to using an abstract class for java dsl
* Wip, playing with not needed classes
* Docs ported to java and removal of the class objects
* java docs for recovery and tagging
* Request response and actor-to-actor-ask
* Outside of actor ask
* Review feedback plus simplification of tell sample
* ask and mention symbolic
* Final sample and some proof reading feedback adressed
* Tests should pass in InteractionPatternSpec
* Incorrect comment removed
* Made sure all scala samples execute, to protect from regression, added forward refereces in text
* Use context logger
* Some minor rewording
* Feedback applied
* Rebase fix
* expectMessageType
* Add dependency snippets to relevant doc sections
* Add 'Dependency' headings
Tried to consistently add them to each section introducing a module, after
the introduction but before the first code sample.
* Make Dependency sections more consistent
* Change more general factories to private
* Typed Streams docs
* Remove BoxedUnit from Java Api
* Use JavaPartialFunction in Java examples
* Doc wording improvements, formatting fixes, no verification diagrams
* Don't apply dilation to scheduler parameter
* Clarify ExecutionContext usage
* Clarify comment on timePasses
* Make ExplicitlyTriggeredScheduler internals private
* List currently scheduled tasks in one log message
* Execute immediately if (initialDelay <= Duration.Zero)
* Don't reschedule if scheduled task fails
* Be more efficient about logging
* Widen `timePasses` delay for now
https://github.com/akka/akka/pull/24243#discussion_r160985493 for some
discussion on what to do instead
* Remove mechanism for mixing in config from a test trait
* Replacement of spawnAdapter, we could could keep spawnAdapter as
an internal feature (we know about the resource leak risk)
* The new ActorContext.messageAdapter can be used in the
same way as spawnAdapter but without the risk of unbounded
resource leak.
* Only one message transformer per class is supported to avoid
unbounded growth of registered transformers in case they are
registered repeatedly. That is also a way to replace transformers,
if that would be needed.
* It's still encouraged to register the transformers in a top level
deferred, but other usages are possible. It would still be wrong
to capture incoming message specific context in the transformer
function.
* The transformation function is run inside the actor.
* One single spawnAdapter ref is used for all transformers. It wraps
the message in an internal Transform message.
* rename to spawnMessageAdapter and only kept it as internal in scaladsl
* update chat room example to use child actors
* docs
