--
You received this message because you are subscribed to the Google Groups ".NET HTTP Abstractions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstrac...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstractions+unsub...@googlegroups.com.
Yep spec needs fixing here. Want to send a PR to the 1.1 MD with better text? :)
You received this message because you are subscribed to a topic in the Google Groups ".NET HTTP Abstractions" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/net-http-abstractions/CB87zpxnbLo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to net-http-abstrac...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstractions+unsubscri...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups ".NET HTTP Abstractions" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/net-http-abstractions/CB87zpxnbLo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to net-http-abstractions+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstrac...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstrac...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstrac...@googlegroups.com.
Why can't you just have one term "middleware" and do away with "app". Which to me seems outside the scope of a spec like this?
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstractions+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstrac...@googlegroups.com.
I agree with Ryan (and possibly Seb?) that App is the whole thing - composed of all different middlewares. As such App <--> Framework cannot be correct: app can mix different frameworks and probably MW <---> Framework.My view is that there is no need for builder function since they are framework dependent. There can be many builders, each suited to their own frameworks. Having said that, we need MW and pipeline interfaces defined. which seems you have already done??
On Thursday, 19 June 2014 12:06:46 UTC+1, SerialSeb wrote:
I assume your middleware base class provides the conversion from Env to IContext?Way I see it, Server/Host-> AppFunc. The fact that AppFunc may be a framework, may be a framework with decorators, or that all are decorators and AppFunc is just a env=>MidFunc(null) is dependent on having MidFunc. So I think in the new MidFunc world it makes sense to change the text, but how you slice and dice it, which assemblies it lives in or how you do the actual wireup is really out of the scope of the spec.Let’s fix the text to make this more palpable and explain this more explicitly as we do the updates for MidFunc and BuildFunc?
On Tuesday, June 10, 2014 11:43:41 AM UTC-4, Ali Kheyrollahi wrote:Hi guys,This is my first here.So there have been a few niggling things in the back of my mind which I believe needs some work especially now that we are considering v1.1 of spec.Currently the difference between web app and middleware is poorly defined. Where I stand is that I think there is no difference, an app could be pass through if we think of OWIN HTTP pipeline as a linear structure. One example is a set of apps that each work on a particular route and ignores the rest.So I am missing something? Anybody else feel the same?
--
Should BuildFunc be a part of the MidFunc spec, or a separate spec? Think I'd prefer the latter myself.