Documentation
¶
Overview ¶
Package messaging provides message service features which enables agent framework to handle any incoming DIDComm message based on their type and purpose. Incoming message of type not handled by any of the existing protocol services will be handled by available message service of matching type and purpose.
This package provides message service provider implementation `msghandler` which can be used to maintain list of available message services. (RFC Reference : https://github.com/hyperledger/aries-rfcs/blob/master/features/0351-purpose-decorator/README.md)
This package also provides custom message service implementation under `service` package, one which is `service/http` for `http-over-didcomm` service. (RFC Reference : https://github.com/hyperledger/aries-rfcs/blob/master/features/0335-http-over-didcomm/README.md)
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
Package msghandler dynamically maintains the list of registered message services.
|
Package msghandler dynamically maintains the list of registered message services. |
|
service
|
|
|
basic
Package basic provide basic message protocol features Any incoming message of type "https://didcomm.org/basicmessage/1.0/message" can be handled by registering `basic.MessageService`.
|
Package basic provide basic message protocol features Any incoming message of type "https://didcomm.org/basicmessage/1.0/message" can be handled by registering `basic.MessageService`. |
|
http
Package http provides http-over-didcomm message service features.
|
Package http provides http-over-didcomm message service features. |