Expand description
§No-Op Transport Implementation
This module provides a stub transport implementation that handles M2M requests without performing any actual network communication. It’s designed for scenarios where distributed functionality is disabled or not needed, such as single-node deployments or testing isolated middleware behavior.
§Behavior
The no-op transport responds to all M2M requests with sensible default values:
- Destination Compliance: Returns default policy (public, integrity 0, not deleted, consent given)
- Source Compliance: Returns empty policy map (no source policies)
- Update Provenance: Acknowledges the request without action
§Use Cases
- Single-node deployments where distributed features are unnecessary
- Testing middleware logic in isolation without network dependencies
- Fallback transport when network communication is disabled
- Development environments where distributed setup is not feasible
Structs§
- M2mNop
- No-operation transport service for M2M communication.