-
-
Notifications
You must be signed in to change notification settings - Fork 364
Outgoing step context
Mogens Heller Grabe edited this page Aug 20, 2015
·
1 revision
The outgoing step context is a context object that is created for each sent message and will be passed down through the pipeline of outgoing message steps.
The outgoing step context is initialized with the outgoing Message, the current ITransactionContext, and the list of destination addresses in the form of a DestinationAddresses object (under their default keys, i.e. determined by their types) for the rest of the pipeline to use.
Basic stuff
- Home
- Introduction
- Getting started
- Different bus modes
- How does rebus compare to other .net service buses?
- 3rd party extensions
- Rebus versions
Configuration
Scenarios
Areas
- Logging
- Routing
- Serialization
- Pub sub messaging
- Process managers
- Message context
- Data bus
- Correlation ids
- Container adapters
- Automatic retries and error handling
- Message dispatch
- Thread safety and instance policies
- Timeouts
- Timeout manager
- Transactions
- Delivery guarantees
- Idempotence
- Unit of work
- Workers and parallelism
- Wire level format of messages
- Handler pipeline
- Polymorphic message dispatch
- Persistence ignorance
- Saga parallelism
- Transport message forwarding
- Testing
- Outbox
- Startup/shutdown
Transports (not a full list)
Customization
- Extensibility
- Auto flowing user context extensibility example
- Back off strategy
- Message compression and encryption
- Fail fast on certain exception types
Pipelines
- Log message pipelines
- Incoming messages pipeline
- Incoming step context
- Outgoing messages pipeline
- Outgoing step context
Prominent application services