Hey folks, OWIN v1.0.0-RC0 is now live on owin.org.http://owin.org/spec/owin-1.0.0-RC0.html We are now entering the final two week comment period. If there is no significant feedback by Wednesday October 10th, v1.0.0-RC0 will become the final v1.0.0. Anyone and everyone PLEASE read, proof-read, implement, and otherwise dissect the RC0 spec so we can identify any lingering issues. Thanks, and well done everybody!~Chris R
Reminder, the comment deadline for OWIN v1.0 is this Wednesday.
Given the lack of comments so far, PLEASE respond if you have at least read v0.15 or v1.0-RC?http://owin.org/spec/owin-1.0.0-RC0.html Thanks,~Chris RFrom: tratc...@hotmail.com
To: net-http-abstractions@googlegroups.com
Subject: OWIN v1.0.0 Last Call
Date: Thu, 27 Sep 2012 09:46:03 -0700
We are now entering the final two week comment period. If there is no significant feedback by Wednesday October 10th, v1.0.0-RC0 will become the final v1.0.0.
Anyone and everyone PLEASE read, proof-read, implement, and otherwise dissect the RC0 spec so we can identify any lingering issues.
--
Louis - sent from mobile
------------------------------
From: Chris R
Sent: 10/8/2012 10:32 AM
To: net-http-abstractions@googlegroups.com
Subject: RE: OWIN v1.0.0 Last Call
Reminder, the comment deadline for OWIN v1.0 is this Wednesday.
We are now entering the final two week comment period. If there is no
significant feedback by Wednesday October 10th, v1.0.0-RC0 will become the
final v1.0.0.
Anyone and everyone PLEASE read, proof-read, implement, and otherwise
dissect the RC0 spec so we can identify any lingering issues.
I said the same thing back when OWIN first reached, if only for a brief moment, 1.0, but I am going to say it again. Why the rush? Why put something at 1.0 that's not even been given proper testing in the wild? The way I see it, the members of this user group pretty much are in control of the entire echosystem of frameworks and servers that would be first to implement the specification and after that, and only then, will the general public start to use OWIN (no matter what version the specification is at) and write middleware for it. When it reaches the wider audience there are bound to be a lot of edge cases pop up that will (hopefully) have an impact on the design as it moves forward
The RC is more or less an "private club release candidate" because John Doe's not taken it for a spin.. a selective few has? Am I missing something here? =)
On Monday, October 8, 2012 8:35:23 PM UTC+2, Louis DeJardin wrote:
> Read it. +1
> -- > Louis - sent from mobile > ------------------------------ > From: Chris R > Sent: 10/8/2012 10:32 AM > To: net-http-a...@googlegroups.com <javascript:> > Subject: RE: OWIN v1.0.0 Last Call
> Reminder, the comment deadline for OWIN v1.0 is this Wednesday.
> We are now entering the final two week comment period. If there is no > significant feedback by Wednesday October 10th, v1.0.0-RC0 will become the > final v1.0.0.
> Anyone and everyone PLEASE read, proof-read, implement, and otherwise > dissect the RC0 spec so we can identify any lingering issues.
On Tuesday, October 9, 2012 6:08:56 AM UTC-5, Andreas Håkansson wrote:
> I said the same thing back when OWIN first reached, if only for > a brief moment, 1.0, but I am going to say it again. Why the rush? Why put > something at 1.0 that's not even been given proper testing in the wild? The > way I see it, the members of this user group pretty much are in control of > the entire echosystem of frameworks and servers that would be first > to implement the specification and after that, and only then, will the > general public start to use OWIN (no matter what version the specification > is at) and write middleware for it. When it reaches the wider audience > there are bound to be a lot of edge cases pop up that will (hopefully) have > an impact on the design as it moves forward
> The RC is more or less an "private club release candidate" because John > Doe's not taken it for a spin.. a selective few has? Am I missing something > here? =)
I see what you are saying Andreas, but I would also ask why leave it at 0.X for a really long time when we really do some things running on this? I think the model is (now) very simple. We also have a solid versioning strategy, so we can always version it later. This is also a spec; the implementations in Gate, Katana, etc. can all be versioned and fixed independently. I'm happy to have a flag shoved in the ground at this point. I think that may be necessary broader adoption in the Microsoft space, despite that not being the case in other dev cultures.
I'm actually waiting for it to hit 1.0 before sending my ServiceStack OWIN host pull request and attempting to implement it for RavenDB. The owners of these projects, and myself as a contributor, don't really want to consider supporting this until 1.0 is officially released. It's a bit chicken-n-egg, you may not get 'proper testing in the wild' until after 1.0 is released.
On Tuesday, 9 October 2012 12:08:56 UTC+1, Andreas Håkansson wrote:
> I said the same thing back when OWIN first reached, if only for > a brief moment, 1.0, but I am going to say it again. Why the rush? Why put > something at 1.0 that's not even been given proper testing in the wild? The > way I see it, the members of this user group pretty much are in control of > the entire echosystem of frameworks and servers that would be first > to implement the specification and after that, and only then, will the > general public start to use OWIN (no matter what version the specification > is at) and write middleware for it. When it reaches the wider audience > there are bound to be a lot of edge cases pop up that will (hopefully) have > an impact on the design as it moves forward
> The RC is more or less an "private club release candidate" because John > Doe's not taken it for a spin.. a selective few has? Am I missing something > here? =)
> On Monday, October 8, 2012 8:35:23 PM UTC+2, Louis DeJardin wrote:
>> Read it. +1
>> --
>> Louis - sent from mobile
>> ------------------------------
>> From: Chris R
>> Sent: 10/8/2012 10:32 AM
>> To: net-http-a...@googlegroups.com
>> Subject: RE: OWIN v1.0.0 Last Call
>> Reminder, the comment deadline for OWIN v1.0 is this Wednesday.
>> We are now entering the final two week comment period. If there is no >> significant feedback by Wednesday October 10th, v1.0.0-RC0 will become the >> final v1.0.0.
>> Anyone and everyone PLEASE read, proof-read, implement, and otherwise >> dissect the RC0 spec so we can identify any lingering issues.
Yes, this is about adoption. There are several platforms that have prototyped OWIN but are unwilling to deploy it until 1.0. Conversely I'm not aware of anyone that has committed to deploy the RC version. As Ryan said, between the extension and versioning models it shouldn't be too difficult to address any gaps we may find in production.Date: Tue, 9 Oct 2012 05:57:51 -0700
From: dhic...@gmail.com
To: net-http-abstractions@googlegroups.com
CC: tratc...@hotmail.com
Subject: Re: OWIN v1.0.0 Last Call
I'm actually waiting for it to hit 1.0 before sending my ServiceStack OWIN host pull request and attempting to implement it for RavenDB. The owners of these projects, and myself as a contributor, don't really want to consider supporting this until 1.0 is officially released. It's a bit chicken-n-egg, you may not get 'proper testing in the wild' until after 1.0 is released.
On Tuesday, 9 October 2012 12:08:56 UTC+1, Andreas Håkansson wrote:I said the same thing back when OWIN first reached, if only for a brief moment, 1.0, but I am going to say it again. Why the rush? Why put something at 1.0 that's not even been given proper testing in the wild? The way I see it, the members of this user group pretty much are in control of the entire echosystem of frameworks and servers that would be first to implement the specification and after that, and only then, will the general public start to use OWIN (no matter what version the specification is at) and write middleware for it. When it reaches the wider audience there are bound to be a lot of edge cases pop up that will (hopefully) have an impact on the design as it moves forward
The RC is more or less an "private club release candidate" because John Doe's not taken it for a spin.. a selective few has? Am I missing something here? =)
On Monday, October 8, 2012 8:35:23 PM UTC+2, Louis DeJardin wrote:Read it. +1
--
Louis - sent from mobile
From: Chris R
Sent: 10/8/2012 10:32 AM
To: net-http-a...@googlegroups.com
Subject: RE: OWIN v1.0.0 Last Call
Reminder, the comment deadline for OWIN v1.0 is this Wednesday.
We are now entering the final two week comment period. If there is no significant feedback by Wednesday October 10th, v1.0.0-RC0 will become the final v1.0.0.
Anyone and everyone PLEASE read, proof-read, implement, and otherwise dissect the RC0 spec so we can identify any lingering issues.
OWIN v1.0.0 is now live on owin.org Enjoy :-)From: tratc...@hotmail.com
To: net-http-abstractions@googlegroups.com
Subject: RE: OWIN v1.0.0 Last Call
Date: Tue, 9 Oct 2012 09:02:06 -0700
Yes, this is about adoption. There are several platforms that have prototyped OWIN but are unwilling to deploy it until 1.0. Conversely I'm not aware of anyone that has committed to deploy the RC version.
As Ryan said, between the extension and versioning models it shouldn't be too difficult to address any gaps we may find in production.
Date: Tue, 9 Oct 2012 05:57:51 -0700
From: dhic...@gmail.com
To: net-http-abstractions@googlegroups.com
CC: tratc...@hotmail.com
Subject: Re: OWIN v1.0.0 Last Call
I'm actually waiting for it to hit 1.0 before sending my ServiceStack OWIN host pull request and attempting to implement it for RavenDB. The owners of these projects, and myself as a contributor, don't really want to consider supporting this until 1.0 is officially released. It's a bit chicken-n-egg, you may not get 'proper testing in the wild' until after 1.0 is released.
On Tuesday, 9 October 2012 12:08:56 UTC+1, Andreas Håkansson wrote:I said the same thing back when OWIN first reached, if only for a brief moment, 1.0, but I am going to say it again. Why the rush? Why put something at 1.0 that's not even been given proper testing in the wild? The way I see it, the members of this user group pretty much are in control of the entire echosystem of frameworks and servers that would be first to implement the specification and after that, and only then, will the general public start to use OWIN (no matter what version the specification is at) and write middleware for it. When it reaches the wider audience there are bound to be a lot of edge cases pop up that will (hopefully) have an impact on the design as it moves forward
The RC is more or less an "private club release candidate" because John Doe's not taken it for a spin.. a selective few has? Am I missing something here? =)
On Monday, October 8, 2012 8:35:23 PM UTC+2, Louis DeJardin wrote:Read it. +1
--
Louis - sent from mobile
From: Chris R
Sent: 10/8/2012 10:32 AM
To: net-http-a...@googlegroups.com
Subject: RE: OWIN v1.0.0 Last Call
Reminder, the comment deadline for OWIN v1.0 is this Wednesday.
We are now entering the final two week comment period. If there is no significant feedback by Wednesday October 10th, v1.0.0-RC0 will become the final v1.0.0.
Anyone and everyone PLEASE read, proof-read, implement, and otherwise dissect the RC0 spec so we can identify any lingering issues.
