-
Notifications
You must be signed in to change notification settings - Fork 19
Meeting 24 May 2012
Thursday 24th, 11am pacific
Shape the planning roadmap
https://github.com/owin/owin/wiki/Planning
Proposals for possible timeline
Review inventory of potential implementations
https://github.com/owin/owin/wiki/implementations
Proposals for adding or removing items needed to flush out OWIN problems
Call to action – put names next to items where there is time and interest in committing code
Look at owin-sandbox repo
https://github.com/owin/owin-sandbox
Is this an effective tool to drive out common scenarios
Proposals for additional case studies
Call to action – put names next to items where there is time and interest in committing code
Walk through the delegate signature as it stands
https://github.com/owin/owin/blob/master/src/main/Owin/Owin.cs
Proposals for changes and concerns to be resolved in delegates
Discuss role of Gate.Request and Gate.Response utility classes
https://github.com/owin/gate/blob/master/src/Main/Gate/Request.cs
https://github.com/owin/gate/blob/master/src/Main/Gate/Response.cs
Discuss possible benefit of “internal class” code-only Gate.Sources nupkg
Proposals for changes and concerns to be resolved in Gate utility classes
Roadmap sounds fine
Need to dial in scope of and qty of implementation before seeing what timeline would look like
Highest priority implementation for "critical mass" are Microsoft intrinsics
Examples like ASP.NET and WebAPI are key for general adoption rates
ASP.NET, HttpListener, and to some extent IIS Native Module are key for general adoption rates
First class Mono support
Sake is a good step in that direction
Maintaining a "green-light" on teamcity for .net and mono is key
Being able to run c# web apps on mac w/out parallels would be fantastic
Out-of-box middleware isn't something you can really pin down in advance
Incubating middleware in gate contribs would be good.
Knowing how to discover middleware on nuget would be good.
A test harness for http correctness, stress, performance and stability would be key
Running the harness against any hosting option would be fantastic
Autobahn is an example of that kind of thing that tests correctness of any WS server implementation
Followup: does such a thing exist for http correctness? [loudej]
- Redbot ?
Call to action on implementations
put time on ms-specific tech [loudej]
put time on http test harnesses [loudej]
github / owin / owin-sandbox contains a series of case studies to explore end-user experience in various mini scenarios
static file server is a good case study to add [loudej]
signalr + nancy is another to add [loudej]
chunked data forever is another [loudej]
websockets is yet another [loudej]
brief note - anyone can feel free to jump in on adding code as well, if they like :)
brief walk through the delegates and iappbuilder interface
option a - draft 5
isasync = write(data, ()=>continue);
option b - in code
isbuffering = write(data); isasync = flush(()=>continue);
option a - draft 5
IDictionary<string,string>
option b - in code
IDictionary<string,IEnumerable<string>>
option c - for consideration
IDictionary<string,string[]>
option a - in code
Task<Tuple<string, IDict<string,IEnum<string>>, BodyDelegate>>
option b - for consideration
Task<OwinResponse>; struct OwinResponse { string Status, IDict headers, BodyDelegate body }
option a - in code
result(string, IDict<string,IEnum<string>>, BodyDelegate)
option b - for consideration
result(response); struct OwinResponse { string Status, IDict headers, BodyDelegate body }
option a - in code
- nothing, context at startup is application-specific solution
option b - for consideration
-
IDictionary<string,object> IAppBuilder.Propertiesfor intra-component (host/middleware/fwk/site) context at startup
some ad-hoc discussion of IAppBuilder's role
brief look at owin-sandbox to illustrate use of IAppBuilder in end-user code
time ran out and the meeting was kicked from the conference room with the speaker-phone