Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Won't Do
-
None
-
None
-
None
Description
It would be really good to have a protocol independent message abstraction that allows plugins to perform actions independently of the protocol used. Some examples could be developing a protocol independent filter, or sending messages to destinations in a generic way, but I'm sure it would be useful in many other scenarios.
The message abstraction would need to abstract at least the concepts of headers and content of a message to be used in the scenarios described.