This past Monday I published a post with a helper class for relaying HTTP POST requests from one WCF service to another, detailing how to create a relay service in c#. Then I took it down right away. Sorry about that…
Here’s what happened: I wrote the code to solve a problem at work on the Friday before that. It took a couple of hours and the code was written inside my WCF service implementation. Then on the Sunday when I wrote the blog post, I refactored that code into a generic helper class, making it different to my code at work. The helper class changed the WCF service such that each endpoint’s code became a one line call to the helper, which was why I saw value in sharing it. Then I scheduled the blog post for 5PM (South African time) on Monday.
However, on Monday I refactored my work code to use that helper class, and published the service. The end result was that apart from the namespace and the service itself (because the code is meant to help create a relay out of any such WCF service), the code on my blog was identical to the code of a service running in production. Even though it did not reveal anything of my employer’s business, that’s not the point. The point is, since I used the code for a production service, it is not my intellectual property.
Maybe some time in future, time permitting, I can extend the class into a framework that handles other Http verbs, and serializes JSON as well as XML. And then I can republish it here. But until then, that is not code I can share.