For starters, I had to examine if the router service supports all the common bindings we’ve been using in our enterprise.
The following worked just fine:
- BasicHttp
- Http Protocol, Text Encoding and Soap12 Message Version (part of the WS-I Basic Profile)
- WsHttp
- Standard
- Reliable Session (instead for O/W – more at the next post)
- NetTcp
- Standard
- Reliable Session
For the relevant bindings above, sessionful contracts were preserved and transactions were propagated – as long as I configured everything correctly.
Unfortunately, I didn’t get WebHttp (Implementing RESTful services) to work through the router service, I didn’t dive into all the bits and bytes so perhaps there is a way to somehow make it work but I didn’t find a way to do that so far. This is the first point of failure.
Concluding failure points:
- WebHttp isn’t supported as much as I could tell