sbt 0.10

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

sbt 0.10

n8han
Administrator
I've merged in Doug's sbt 0.10 branch as part of the upcoming release. You'll need to use sbt 0.10 to build Unfiltered from here on out.

Nathan
Reply | Threaded
Open this post in threaded view
|

Re: sbt 0.10

chris_lewis
Awesome - high-five him for me.

On 7/12/11 2:07 PM, n8han [via Databinder] wrote:
I've merged in Doug's sbt 0.10 branch as part of the upcoming release. You'll need to use sbt 0.10 to build Unfiltered from here on out.

Nathan


If you reply to this email, your message will be added to the discussion below:
http://databinder.3617998.n2.nabble.com/sbt-0-10-tp6576184p6576184.html
To start a new topic under Unfiltered, email [hidden email]
To unsubscribe from Unfiltered, click here.

Reply | Threaded
Open this post in threaded view
|

new header extractors and appliers (was: sbt 0.10)

n8han
Administrator
I also just landed Doug's header refactoring branch master. This is
going to be the *big* change in 0.4.0.

The original header extractors were highly influenced by the servlet
spec; they assume that any header-field could occur more than once. The
new version is highly influenced by the HTTP spec and assumes that if
you are using a particular header-field extractor you expect the request
to conform to spec for that header-field.

The upshot is that now you don't have to pull the head of a sequence for
things that should not be sequences, like IfNoneMatch.

The minor downside is that if you want to handle non-spec inputs, you'll
need to go to the underlying request object or make your own header
extractor for that header-field. The bigger, but temporary, downside is
that you'll need to change most of your code that uses the built-in
header extractors when you upgrade to 0.4.0.

If you have time take look and see if there's anything you think should
be changed before the release.

Nathan