From 826692b0c6ec730c5245f87d23519408002d705c Mon Sep 17 00:00:00 2001 From: anthonyjchriste Date: Fri, 7 Mar 2014 23:09:22 -1000 Subject: [PATCH] Added guides subdirectory to links. --- guides/documentation/hello-world-service.md | 4 ++-- guides/documentation/service-async.md | 4 ++-- guides/documentation/service-interceptors.md | 4 ++-- guides/documentation/service-sse.md | 4 ++-- guides/documentation/service-streaming.md | 4 ++-- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/guides/documentation/hello-world-service.md b/guides/documentation/hello-world-service.md index bc3498be4..d97339e4b 100644 --- a/guides/documentation/hello-world-service.md +++ b/guides/documentation/hello-world-service.md @@ -206,6 +206,6 @@ nil ## Where To Go Next For more about building out the server side, you can look at -[Routing and Linking](/documentation/service-routing.md) or -[Connecting to Datomic](/documentation/connecting-to-datomic.md). +[Routing and Linking](/guides/documentation/service-routing.md) or +[Connecting to Datomic](/guides/documentation/connecting-to-datomic.md). diff --git a/guides/documentation/service-async.md b/guides/documentation/service-async.md index 8d33084a6..b246afccb 100644 --- a/guides/documentation/service-async.md +++ b/guides/documentation/service-async.md @@ -104,6 +104,6 @@ Pedestal's built in support for server-sent events works. _io.pedestal.impl.inteceptor_ namespace. The code in this namespace is subject to change.) -For more about streaming, see [Streaming Responses](/documentation/service-streaming.md). For more -about SSE, see [Server-Sent Events](/documentation/service-sse.md). +For more about streaming, see [Streaming Responses](//guidesdocumentation/service-streaming.md). For more +about SSE, see [Server-Sent Events](/guides/documentation/service-sse.md). diff --git a/guides/documentation/service-interceptors.md b/guides/documentation/service-interceptors.md index c4acde36a..10116002c 100644 --- a/guides/documentation/service-interceptors.md +++ b/guides/documentation/service-interceptors.md @@ -88,7 +88,7 @@ Interceptors aim to explicitly solve the issue of request processing being coupled tightly to one thread. It does this with two mechanisms: 1. Interceptors operate on a - [context](/documentation/service-context-reference.md) which + [context](/guides/documentation/service-context-reference.md) which explicitly retains all data associated with processing one request. @@ -306,7 +306,7 @@ You can port Ring code to Pedestal by: - If you are using Compojure for routing requests, rewrite your route definitions using the terse routing format (see - [Service Routing](/documentation/service-routing.md)). Any Ring middlewares that run + [Service Routing](/guides/documentation/service-routing.md)). Any Ring middlewares that run before your Compojure routes should be replaced by interceptors that run before routing. Any middlewares specified in your Compojure routes should be replaced by interceptors referenced directly in diff --git a/guides/documentation/service-sse.md b/guides/documentation/service-sse.md index c8f2f6e33..0d87fa170 100644 --- a/guides/documentation/service-sse.md +++ b/guides/documentation/service-sse.md @@ -36,7 +36,7 @@ requests to an interceptor returned from the _io.pedestal.http.sse/start-event-stream_ function. The resulting SSE interceptor processes a request by: -- pausing interceptor execution (see [Service Async](/documentation/service-async.md)) +- pausing interceptor execution (see [Service Async](/guides/documentation/service-async.md)) - sending the appropriate HTTP response headers to tell the client that an event stream is starting. @@ -108,7 +108,7 @@ send. It is important to understand that the server-sent events infrastructure uses the low-level streaming mechanism described -[here](/documentation/service-streaming.md). As such, it is subject to the major +[here](/guides/documentation/service-streaming.md). As such, it is subject to the major limitation of that approach: once events have been streamed, any interceptors that post-process the response from the SSE interceptor will not be able change what was sent on the wire. Interceptor paths diff --git a/guides/documentation/service-streaming.md b/guides/documentation/service-streaming.md index b394ab744..47e753aaf 100644 --- a/guides/documentation/service-streaming.md +++ b/guides/documentation/service-streaming.md @@ -55,7 +55,7 @@ The thread completing the interceptor path will write the body out to the HTTP response stream. If the request is processed synchronously, the work will be done on the Web server thread. If the request is processed asynchronously, the work will be done on whatever thread -resumed processing (see [Service Async](/documentation/service-async.md)). +resumed processing (see [Service Async](/guides/documentation/service-async.md)). Here is an example of an interceptor that returns an arbitrarily large volume of data. @@ -111,5 +111,5 @@ determine whether a response has already been sent by an SSE (or equivalent) interceptor. This functionality is used to implement Server-Sent Events, -documented [here](/documentation/service-sse.md). +documented [here](/guides/documentation/service-sse.md).