That would be a correct assumption. Ciste was born out of my needing
wanting these functions for my own use.
In my own project I'll serve the same record as Atom, XML, 2 different
variants of JSON, RDF/XML, Turtle, edn (clojure), and HTML. Using
defsection allows me to only think about the type of views over a
collection I want to have and then not need to worry about what
environment the view gets rendered in. For instance, show-section will
return a data structure of the appropriate type for the downstream
formatter to transform. This allows me to work in Hiccup everywhere I'm
doing view type things and the actual transform happens at the end.
The other goal of Ciste was to have a module based system where common
clojure libraries could be wrapped with some configuration options and
then mixed in to the system to extend its functionality.
On Fri, Dec 28, 2012 at 12:33 PM, larry google groups
<
lawrenc...@gmail.com> wrote:
> So, am I right to say the Ciste framework is geared toward serving up APIs?
> In multiple formats and over multiple protocols?
>
https://groups.google.com/d/msg/compojure/-/qoD6mvfP-EcJ.