Document middleware phases

[bajtos]

Update the middleware documentation page in Confluence and describe the new features related to middleware phases:

http://docs.strongloop.com/display/LB/Defining+middleware

A draft of the new content:

https://gist.github.com/bajtos/e7eaba736ff096916b71

Before we can publish the new content, the following tasks must be finished:

• Land #68 - Implement shorthand notation for middleware paths loopback-boot#70
• Release a new minor version of loopback-boot (v2.4.0)

Nice to have:

• Update api-server template to use the new declarative middleware registration loopback-workspace#167

[bajtos]

@crandmck as I was going through the steps listed in https://github.com/strongloop-internal/scrum-loopback/issues/54, I realised the docs is missing information on how to package custom middleware handlers. Please add the following information to the docs.

I want to create a new component project (npm package) to share middleware
implementations between multiple projects.

Create a new package that exports a middleware constructor function. See Middleware Constructor for details.

In my existing component project created via slc loopback, I want to implement a new middleware handler and share it with other projects.

Place the file with the middleware constructor to the directory server/middleware, e.g. server/middleware/myhandler.js.

[crandmck]

Added http://docs.strongloop.com/display/LB/Using+middleware+phases#Usingmiddlewarephases-Packagingcustommiddlewarehandlers
@bajtos please review.

[bajtos]

Will take a look ASAP next week.

[bajtos]

http://docs.strongloop.com/display/LB/Using+middleware+phases#Usingmiddlewarephases-Built-inmiddleware

(Copy the table from Express middleware and remove favicon entry, as it was already described above.)

I left a placeholder that should have been replaced by content from the old page, the placeholder is still there. Could you please fix that?

[bajtos]

http://docs.strongloop.com/display/LB/Using+middleware+phases#Usingmiddlewarephases-Examples

The example at the end of "Pre-processing middleware" section should show console output. At the moment, there is a copy of the code.

See the gist:

...
Request tracking middleware triggered on /.
The request processing time is 4.281957 ms. //your results will vary