Axum and the CCR: what and how?

This is copied verbatim from a MSDN Forums post about how Axum uses parts of the CCR:

Here's what we did:

1. We took the CCR sources, changed most of the names, slightly refactored the interfaces and added a few things.
2. We built it into Microsoft.Axum.Runtime.dll
3. We built channel ports on top of CCR Ports (renamed OrderedInteractionPoints).
4. We exposed OIP to programmers (see the WebFetcher sample).
5. We built 'async,' 'sync,' and 'const' empty/full storage capabilites on some additions we made to CCR.
6. The 'receive' expression utilizes a Receiver to hook into the source.

One reason for the rename is that in the CTP, you really need to use the Axum capabilities (data-flow networks, receives, etc.) to program the local (within-domain) message-passing capabilites, and we didn't want to create another distribution of the CCR. If you want to use CCR, please get it separately, as it is not currently safe to use with Axum unless you go through the language capabilities. It is likewise not generally safe to create your own threads from within an Axum domain, and there is no need to.

Source