+str #24229 remove protobuf changes, which do not need to be made in this PR
docs
moved things
config object
subscription timeout confifmed working, also, attributes
document attributes for sub timeout
tests for the source also failing when it should
additional demand test
implemented protection from materializing "in cycles"; would be nice in
types but that breaks the niceness of use of the types
SinkRef/SourceRef...
cleanup
no idle timeout built in, can use the Timeout stages
more docs
simplest change to prevent exposing SinkRef => SourceRef => SinkRef cycle
Things to decide:
* is it ok to require using `getSource` / `getSink` as Java API, is there better naming?
* where should the constructors go? I'd say just in regular javadsl/scaladsl `Source`/ `Sink` objects
move constructors to {javadsl,scaladsl}.{Source,Sink} companion objects
Remove now useless "canMaterialize" field
Separate stage (implementation) from ref (wrapped actor ref) to make it clearer what is serialized
Clarify that partner refs are not optional in on-the-wire interfaces
minor cleanup in SourceRefStage
Renamed the stages but questionable if that really helps ;)
cleanups, better docs
cleanup, fix docs compilation
fix mima
got rid of Futures in the materialized values of stream refs
silly serialization mistake, should have fixed serialize as well
tage actors now can have names, which helps a lot in debugging
thread weirdness
make sure to fail properly, actually go over remoting
issue with not receiving the SinkRef... what
initial working SinkRef over remoting
remote Sink failure must fail origin Source as well
cleaning up and adding failyre handling
SinkRef now with low-watermark RequestStrategy
source ref works, yet completely duplicated code
* The technical reason for not naming it Behavior is that
it would be duplicate import conflicts of
akka.actor.typed.Behavior and akka.actor.typed.scaladsl.Behavior
* Plural naming is pretty common for factories like this,
e.g. java.util.Collections
* Allow tagging in persistence typed (#23817)
* Use Set[String] for tags
* Documentation for persistence typed tagging
* Rename tagging parameter to tagger
* +rem #24265 protobuf serializer for Address and UniqueAddress in akka-remote
* remove the duplication, by using previously existing type
* fixed doc link
* make it easier to enable the additional no-java-serialization bindings
* fixed akka-actor failure due to changes
* cleanup
* Update reference.conf
* Update serialization.md
* Update reference.conf
* Always add sender of GetContacts to client interactions
* Handover clients when receptionist leaves the cluster
* Revision based on code review
* Cluster receptionist only tracks connected clients
* Initial pass of typed testkits
Not expecting this to be the final API just want to get some
examples documented and internals hidden
Refs #23667 and #22764
Creates the following modules:
akka.actor.typed
akka.persistence.typed
akka.cluster.typed
akka.cluster.sharding.typed
Differences from untyped:
DData and cluster singleton are inside cluster. DData is in the package akka.cluster.dddata.typed
Refs #23632
We also probably want to add some more wording explaining you probably don't
want to use remoting directly, but either use a 'proper' protocol like
akka-http to loosely couple or akka-cluster for more coupled systems, but that
could be another PR
Move 'networking' below 'streams' as you don't typically have to deal with it directly
* Revert "fix entityPropsFactory id param, #21809"
This reverts commit cd7eae28f6.
* Revert "Merge pull request #24058 from talpr/talpr-24053-add-entity-id-to-sharding-props"
This reverts commit 8417e70460, reversing
changes made to 22e85f869d.
* AllPersistenceIdsQuery -> PersistenceIdsQuery
* Replaced additional instances of old name allPersistenceIDs with new persistenceIDs in docs and comments
