On 16/11/13 21:22, Craig wrote:
Very interesting. I have a similar requirement, but not in serving web
requests. I haven't looked under the covers of your module, but wonder
if it could be decoupled from web/ring?
Craig
Yes - I don't think that would be at all difficult. The only
HTTP-specific bit is that I expect {:status 503} to mean "Overloaded" -
assuming you already have functions that take a request and return a
response, something that the function should return if it's overloaded
(i.e. the analogue to {:status 503}) and (optionally) some way of
telling if the wrapped function is reporting overload (the equivalent of
#(= 503 (:status response)) then it should be quite easy to apply it to
other protocols.
Rob
--
--
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/groups/opt_out.
