i've just joined because, well, it was a click away. my coworker tried to use liberator and it worked at first, but then somewhat failed for him which made him go back to ring + middlewares like i do.
but i'm curious anyway.
Andy, we've made some attempts with liberator in one of our search oriented services, but did not find it to be a great fit for non-CRUD type services. We're planning other services, though, and will try liberator again with those that are more suitable for a real ReSTful framework. How about you?
I think for simple needs, liberator is too big. But of course, often simple things evolve into complex and then one regrets not having used the proper tools in the beginning :)
But that might depend on your story, the PUT/POST path is not super well supported, yet, if it comes to processing the request entity (body).
And of course, this is as much a clojure issue as it might be a liberator issue.
If-Modified-Since does not require the clocks of the client and the server to be in sync, but as it works only on 1 second granularity due to the time format used, it is not suitable for resources that change frequently and it can even fail with rarely changing resources if two updates happen in the same second and the client fetches the first version of that second.
Right there, the tutorial also says " A resource can generate an ETag by providing a function at the key :etag", but the example shows just some code snippet, not a function. What is the context in which that piece of code is evaluated? I will need to look at the request to determine the etag, so a contextless expression won't really do, I guess.
@hanshuebner the simples way to plug in custom represenation generation for JSON is to provide a custom function at
:as-responsewhich should accept the data returned by a handler and the context. You can check the media-type in (get-in ctx [:represenation :media-type]) and if it’s json call your json library of choice. For the other media types you can delegate to liberator.representation/as-response.