Project: springxd
Issue XD-162: Create design document for implementation strategy to support message conversion in ChannelRegistry
The conversion should be based on content-type headers, similar to the way Spring's HttpMessageConverters work (with mime types). Also, the map of available converters should be extensible while including the most common defaults (for JSON, XML, etc). We most likely want to add a few of our own content types also (e.g. for Tuples). Most likely, this logic and the configuration methods for extending the converter map, belong in AbstractChannelRegistry since it should be common across all implementations (i.e. the logic should be the same regardless of the transport used after-serialization/before-deserialization).
Story points: 5