Skip to content
This repository has been archived by the owner on Oct 27, 2019. It is now read-only.

Commit

Permalink
removed migration guide from readme
Browse files Browse the repository at this point in the history
  • Loading branch information
tj committed Jul 2, 2011
1 parent b4898dc commit b171880
Showing 1 changed file with 0 additions and 55 deletions.
55 changes: 0 additions & 55 deletions Readme.md
Expand Up @@ -5,61 +5,6 @@
Connect is bundled with over _14_ commonly used middleware, including
a logger, session support, cookie parser, and [more](http://senchalabs.github.com/connect). Be sure to view the 1.0 [documentation](http://senchalabs.github.com/connect/).

## 1.0 Migration Guide

Connect 1.0 is a near-complete rewrite of Connect, with this
comes some changes, including some (minor) API changes,
and removal of a few middleware, which you are welcome to
rip out of previous versions as third-party middleware.

### Middleware Removed

- `cache` cached _everything_. This is less than ideal for dynamic apps, rendering this middleware relatively useless.
- `conditionalGet` blanketed _all_ requests, requiring the entire response to be computed before a response could be concluded. This is extremely wasteful.
- `staticGzip` useless. gzip / ship assets to a CDN
- `gzip` buggy
- `lint` lame

### Middleware Renamed

- `staticProvider` is now `static`
- `bodyDecoder` is now `bodyParser`
- `cookieDecoder` is now `cookieParser`

### Middleware Added

- [limit](http://senchalabs.github.com/connect/middleware-limit.html)
- [profiler](http://senchalabs.github.com/connect/middleware-profiler.html)
- [responseTime](http://senchalabs.github.com/connect/middleware-responseTime.html)

### connect.createServer()

The `connect.createServer()` method is now optional, and equivalent to `connect()`. For example:

connect.createServer(
connect.logger()
, connect.static(__dirname)
).listen(3000);

is the same as:

connect(
connect.logger()
, connect.static(__dirname)
).listen(3000);

When an options _object_ is passed as the first argument it is
assumed to be an https server:

connect({ options here }
connect.logger()
, connect.static(__dirname)
).listen(443);

### Charset

The charset is not longer forced via `mime.type()` resolution, now you must explicitly assign this via `res.charset = 'utf8'` etc.

## Running Tests

first:
Expand Down

0 comments on commit b171880

Please sign in to comment.