bruinbrown / fancyfs Goto Github PK

The basis of the framework, pipelines will be how an application is strung together.

Currently pipelines are implemented as a linked data structure, which means that adding to the end in a safe way is unrealistic. The recursive option takes N! operations (N is number of pipeline elements), which isn't great. The current method uses mutability to set the Next element, once again not great especially in the case that the BaseRequest is a shared object.

Routing will be a pipeline element which should run after authentication etc

Another pipeline element. A number of different options including

• Basic authentication
• Forms authentication
• OWIN should it be hosted on OWIN

Currently the pipeline is entirely synchronous and runs on a basic IHttpHandler. Due to the nature of OWIN and the availability of IHttpAsyncHandler in IIS, it's probably a better option to allow for an async request.

In terms of how to make this work, should each element of the pipeline be switched to an async version? ie each pipeline function takes an Async<Request * Response>. This would lead to a fairly large refactor needed and so would be best done early in the project. ie Before key default pipeline elements are started.

It's not much good if it can't be hosted anywhere so that's the next thing to implement.

The 2 main platforms to initially target will be

• IIS - This implementation is likely to change now though
• OWIN