Browse files

Added guides subdirectory to links.

  • Loading branch information...
1 parent b7e2fdb commit 826692b0c6ec730c5245f87d23519408002d705c @anthonyjchriste anthonyjchriste committed Mar 8, 2014
@@ -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/ or
-[Connecting to Datomic](/documentation/
+[Routing and Linking](/guides/documentation/ or
+[Connecting to Datomic](/guides/documentation/
@@ -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/ For more
-about SSE, see [Server-Sent Events](/documentation/
+For more about streaming, see [Streaming Responses](//guidesdocumentation/ For more
+about SSE, see [Server-Sent Events](/guides/documentation/
@@ -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/ which
+ [context](/guides/documentation/ which
explicitly retains all data associated with processing one
@@ -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/ Any Ring middlewares that run
+ [Service Routing](/guides/documentation/ 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
@@ -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/
+- pausing interceptor execution (see [Service Async](/guides/documentation/
- 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/ As such, it is subject to the major
+[here](/guides/documentation/ 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
@@ -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/
+resumed processing (see [Service Async](/guides/documentation/
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/
+documented [here](/guides/documentation/

0 comments on commit 826692b

Please sign in to comment.