Director, Zolution Software Ltd, currently developing original IP in the shape of a project for the primary education sector, as well as developing Rezolver a fully-portable extensible IOC container, including a rich configuration API.

Currently undertaking senior-level C# work for Willis Insurance Group till end of March 2015 to pay the bills.
Previously a Senior Developer with JobServe in the UK. Designed and built the JobServe Android App - 'Jobs & Career Search', which uses the JobServe Web API which I also developed. I have been a professional developer since March 2004, but started learning back when I was 5 or 6, writing BASIC on the ZX Spectrum.

Skills

C#, Javascript, C++ and (passable) Visual Basic. ASP.Net MVC, the .Net type system and runtime, dynamic code generation and usage (getting good at ANTLR at the moment), and I'm a fierce bugslayer. A particular strength is finding and extracting frameworks to promote reusability.

33 Actions

HTTP Response Header for a unique Request ID for REST serviceproblem with custom headers is they can legitimately be stripped out by proxies. In the end, I went with the Pragma header - it's there to provide a mechanism to send back your own custom data, and it shouldn't be stripped by proxies by default, unless an infrastructure bod explicitly sets it up to be.

HTTP Response Header for a unique Request ID for REST serviceYes it is an option. But something feels hacky about an enveloped response like this. Consider a json operation returning a string; now it's returning a type with two members and clients have to do more work to get their data. Not very restful! I have found a header in the spec that might do it, I'm posting an answer...