Skip to content

Commit b7e747f

Browse files
authored
Handlers header improvement (#6802)
* redo the header size * rewording the header text
1 parent b91887d commit b7e747f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

nservicebus/handlers/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If using the Request-Response or Full Duplex pattern, handlers will probably do
1919

2020
If handling a message in a publish-and-subscribe scenario, see [How to Publish/Subscribe to a Message](/nservicebus/messaging/publish-subscribe/).
2121

22-
### Mapping to name
22+
## Mapping to name
2323

2424
Incoming messages will be mapped to a type using [Assembly Qualified Name](https://msdn.microsoft.com/en-us/library/system.type.assemblyqualifiedname.aspx). This is the default behavior for sharing assemblies among endpoints. When a message cannot be mapped based on Assembly Qualified Name, the mapping will be attempted using [`FullName`](https://msdn.microsoft.com/en-us/library/system.type.fullname.aspx). The following is an example of how NServiceBus gets the type information.
2525

@@ -28,7 +28,7 @@ var fqn = message.GetType().AssemblyQualifiedName;
2828
var fallback = message.GetType().FullName;
2929
```
3030

31-
## Behavior when there is no handler for a message
31+
## No handler for a message
3232

3333
Receiving a message for which there are no message handlers is considered an error and the received message will be forwarded to the configured error queue.
3434

@@ -44,11 +44,11 @@ If it is not possible to design multiple handlers in one of the ways described a
4444

4545
There are a number of techniques for making this change, depending on the type of message:
4646

47-
#### Events
47+
##### Original message is published as an event
4848

4949
If the original message is [published as an event](/nservicebus/messaging/publish-subscribe/), the handlers must be hosted in separate endpoints. Each endpoint receives its own copy of the original message, isolating the failure of one handler from the others.
5050

51-
#### Other messages
51+
##### Original message is sent to an endpoint
5252

5353
If the original message is not published as an event, but rather [sent](/nservicebus/messaging/send-a-message.md) to a specific endpoint, the following techniques may be used (listed from simplest to most complex):
5454

0 commit comments

Comments
 (0)