diff options
| author | Nils Grunwald <nils.grunwald@linkfluence.net> | 2011-02-15 11:31:57 +0100 |
|---|---|---|
| committer | Nils Grunwald <nils.grunwald@linkfluence.net> | 2011-02-15 11:31:57 +0100 |
| commit | f76a21679a91a949000385141b769a5130d6544b (patch) | |
| tree | 92412911dc04bcf2e809cba379a99181e7138869 | |
| parent | added ruby implementation (diff) | |
| download | spore-specifications-f76a21679a91a949000385141b769a5130d6544b.tar.gz | |
clarified the inable-if requirements to selectively enable a middleware
| -rw-r--r-- | spore_implementation.pod | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/spore_implementation.pod b/spore_implementation.pod index a329c19..0ceb22c 100644 --- a/spore_implementation.pod +++ b/spore_implementation.pod @@ -69,9 +69,12 @@ optionaly directly from the file itself). A I<Client implementation> B<MUST> also provide a method to enable or disable spore middlewares at runtime. The order in which the -middlewares are enabled is the order in which the request will go +middlewares are enabled is the order in which the request will go through each middleware, and the inverse order in which the response -will go through each optional middleware postprocessing callback. +will go through each optional middleware postprocessing callback. It +B<MUST> also have a method to selectively enable a middleware or not +for each method according to the method properties in the +specification. If middlewares I<A>, I<B> and I<C> were enabled in this order, then the processing order will be: |