Public static void RegisterContentType(string contentType, Func> functor) The above construct however is ridiculously simple to extend with custom Content-Type handlers such as the method below illustrates. 4/5 different design patterns, 10/15 different classes, abstract factories, and God knows what more. I refer to these buggers as 'symbolic delegates', and I twice created an entire programming language around the axiom.Ĭreating something similar to the above without functional programming structs, such as the ability to pass functions around and use these as first class citizens, would be so difficult I'm not even sure if I want to attempt explaining how it should be done.

Then as my API is getting HTTP requests, I can handle these according to the request's Content-Type, using a well known and strongly typed 'function object' in my code, responsible for transforming any payloads to some internally structured format. The point about the code of course is that it allows me to declare an HTTP request payload function object that's associated with the Content-Type value of my requests. 'multipart/form-data', RequestHandlers.FormDataHandler 'application/x-www-form-urlencoded', RequestHandlers.UrlEncodedHandler

'application/json', RequestHandlers.JsonHandler Static readonly Dictionary> _payloadHandlers =

Half life lambda core