;; necessary dependencies ;; [[org.clojure/clojure "1.4.0"] ;; [ring/ring "1.1.6"]] ;; ------------- ;; Behold the mighty app which we have constructed so far: (require 'ring.adapter.jetty) (require 'ring.middleware.stacktrace) (require 'clojure.pprint) (defn wrap-spy [handler] (fn [request] (println "-------------------------------") (println "Incoming Request:") (clojure.pprint/pprint request) (let [response (handler request)] (println "Outgoing Response Map:") (clojure.pprint/pprint response) (println "-------------------------------") response))) (defn handler [request] {:status 200 :headers {"Content-Type" "text/html"} :body (str "<h1>Hello World!!!!!!!!!!!!!!!</h1>" )}) (def app (-> #'handler (ring.middleware.stacktrace/wrap-stacktrace) (wrap-spy))) (defonce server (ring.adapter.jetty/run-jetty #'app {:port 8080 :join? false})) ;; You can access your greeting at: ;; http://localhost:8080 in your favourite browser. ;; Actually, I think it is nice to see the request and response maps as part of the web page ;; So we can modify our spy function (defn html-escape [string] (str "<pre>" (clojure.string/escape string {\< "<", \> ">"}) "</pre>")) (defn wrap-spy [handler spyname include-body] (fn [request] (let [incoming (with-out-str (println "-------------------------------") (println spyname ":\n Incoming Request:") (clojure.pprint/pprint request))] (println incoming) (let [response (handler request)] (let [outgoing (with-out-str (println spyname ":\n Outgoing Response Map:") (clojure.pprint/pprint (if include-body response (assoc response :body "#<?>"))) (println "-------------------------------"))] (println outgoing) (update-in response [:body] (fn[x] (str (html-escape incoming) x (html-escape outgoing))))))))) (def app (-> #'handler (wrap-spy "what the handler sees" true) (ring.middleware.stacktrace/wrap-stacktrace) (wrap-spy "what the web server sees" false) )) ;; With our spying middleware, we can investigate the subject of parameters ;; point your browser at http://localhost:8080/?doom=sarnath ;; In the map which is presented to app by jetty and ring, there is the key :query-string ;; Which should have the value "doom=sarnath" ;; We could use that directly (defn handler [request] {:status 200 :headers {"Content-Type" "text/html"} :body (if-let [s (request :query-string)] (let [[a b c] (re-matches #"(.*)=(.*)" (request :query-string))] (if (and a b c) (str "<h1>You Have Invoked " b " Upon the City of " c "</h1>") (str "<h1>I do not understand, oh dark master...</h1>" ))) (str "<h1>Hello World!!!!!!!!!!!!!!!</h1>" ))}) ;; But clearly there are issues with that approach. ;; Instead, we can let ring take care of it for us by inserting another piece of middleware: (require 'ring.middleware.params) (def app (-> #'handler (wrap-spy "what the handler sees" true) (ring.middleware.stacktrace/wrap-stacktrace) (ring.middleware.params/wrap-params) (wrap-spy "what the web server sees" false) )) ;; If you have another look at http://localhost:8080/?Doom=Sarnath ;; You'll see that in between the web server and the handler function, wrap-params has inserted ;; another key, :query-params, with the :query-string already split up into a key-value map ;; So we don't need to parse the query string ourselves any more: (defn handler [request] {:status 200 :headers {"Content-Type" "text/html"} :body (if-let [m (request :query-params)] (if (empty? m) (str "<h1>Hello World!</h1>" ) (apply str (for [[k v] m] (str "<h1>You Have Invoked " k " Upon the City of " v "</h1>")))) (str "<h1>Missing :query-params. Have you included ring.middleware.stacktrace/wrap-stacktrace, oh dark master?</h1>" ))})
Blog Archive
-
▼
2013
(52)
-
▼
January
(10)
- Ring: Bringing it All Back Home
- A Warm Welcome to Readers from China (你好世界)
- Regular Expressions in Clojure
- Understanding Ring : A Web App that Keeps its Data...
- Maths Tuition (Cambridge STEP)
- Ring: Using Sessions in a Web Application
- How Sessions Work in Ring
- How Cookies Work in Ring
- Really Rather Overdoing the Interest in How Parame...
- Getting Started with Ring
-
▼
January
(10)
Search This Blog
Tuesday, January 8, 2013
Really Rather Overdoing the Interest in How Parameters Work in Ring
The next interesting bit of the Ring Tutorial http://github.com/ring-clojure/ring/wiki/Parameters is pretty straightforward, but I got carried away a bit.
Subscribe to:
Post Comments (Atom)
Excellent tutorial on ring.. I am curious to know if you found a job in clojure?
ReplyDeleteActually it's a bit ironic. After talking to two companies who wanted me to design web sites for them (in python rather than clojure), and turning them down because web programming looked a bit tedious, I had an idea for a web site of my own.
ReplyDeleteSo I've rented an office and am trying to work out how to write web apps in clojure. (For fun, I think. I can't imagine there's any money in my idea).
I keep getting confused by the behaviour of my own app, and I know from long experience that the best way to get an idea properly lodged in my head is to try to teach it to someone else, or failing that to write a tutorial. So I'm writing ring tutorials in order to learn to use it.
This comment has been removed by the author.
ReplyDeleteSo once again: Great to see your blog back. Your approach is somewhat unique and I'm glad you're popping up in my RSS again.
DeleteAnd I don't know how to comment on Blogger, it seems. ;-)
Thanks a lot for your code, it's great!
ReplyDeleteI was wondering, in trying to wrap my mind around clojure-ring middleware and sessions, do you have any tips?
Thanks!
Vaso, I actually wrote these in order to learn to use ring and understand its middleware and sessions. They're really tidied up versions of my experiments while reading the ring tutorials. When I've left it alone for a while and forgotten, I read through this series to remember. The first one's here:
Deletehttp://www.learningclojure.com/2013/01/getting-started-with-ring.html
You should go through the tutorial, typing every line in and seeing what it does. Play!
When they were written they were executable. If you find anything that doesn't work with modern clojure/ring, let me know, they're probably overdue for an update by now.
And I should add something about how to deploy apps, run on heroku, and add database backed storage for sessions.