Refactor the type hierarchy of inter-Dactor messages to improve flexibility when processing messages using pattern matching as well as to make them more manageable.
Problem Description
Pattern matching messages within Receive methods is not very flexible because of a flat hierarchy of most message types
Unsafe messages that are only meant for use in debugging or testing do not share a common ancestor and might be hard to keep track of so we can later warn or deprecate them for production use
Supporting Information
Possible type hierarchy layout with a focus on improving specificity to support flexible pattern matching:
Refactor Inter-Dactor Message Type Hierarchy
Refactor the type hierarchy of inter-
Dactor
messages to improve flexibility when processing messages using pattern matching as well as to make them more manageable.Problem Description
Receive
methods is not very flexible because of a flat hierarchy of most message typesSupporting Information
akka.actor.Status
Success
,Failure
akka
-frameworkInternalMessageProtocol. InternalMessage
Ping
,Pong
,UpdateMapping
,...
adbms
framework.DefaultMessageProtocol. Status
InsertIntoRelation. Success\|Failure
,SelectAllFromRelation. Success\|Failure
RequestResponseProtocol. Response
<UserOp>.Success\|Failure
,...
RequestResponseProtocol
is already onmaster
Related