Right, either way the compojure route would be the same. (GET
"/:profile-name" [profile-name] ...).
You don't need an extra column in your DB unless you want to do so.
The route/compojure is simply responding to the URL you write out in your
template, or that is requested by some other mechanism.
The change would be in your template, where you decide how to write out
those URLs.
(defn make-profile-url [username]
(let [safe-name (clojure.string/replace username #" " "-")]
(str "/" safe-name)))
;; (make-profile-url "John Smith") => "John-Smith"
or
(defn make-profile-url [username]
(let [safe-name (clojure.string/replace username #" " "")]
(str "/" safe-name)))
;; (make-profile-url "John Smith") => "/JohnSmith"
You can do whatever you like best.
Compojure is at the end, receiving the request. In order for anything to
happen you need to actually put an anchor on your template any way you
want, then write the compojure routes to receive them.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
