Hi,
No URL yet, it's in a design phase now. It's an experiment on replacing
sequences with reducers where possible and one of its part is a reducible
I/O. I've said complected because I like to separate the resource itself
from e.g. the way it is accessed (async or blocking). If your defapi is
Hi Jozef,
Sounds interesting - is it open source / can you give a URL?
Design question: Why are you interpreting resources as a reducible? I can
see that making sense for some resources, but not for others.
As for "complected" - be careful not to confuse this with "composed". It's
perfectl
For timeouts, error-handling, and thread isolation, take a look at
Netflix's Hystrix:
https://github.com/Netflix/Hystrix/tree/master/hystrix-contrib/hystrix-clj
On Monday, September 30, 2013 11:46:03 PM UTC-4, Mikera wrote:
>
> I'm curious about the options for managing APIs in Clojure code in a
Hi,
Your approach seems very complected to me. What I'm currently working on is
the following concept:
A resource type, which can be a file, url, some remote REST/SOAP resource
or e.g. a kestrel queue. Each resource has URI and can be used in following
ways:
- as a regular reducible collection: re
Hi all,
I'm curious about the options for managing APIs in Clojure code in a
relatively idiomatic / consistent / functional way. The features I'm
roughly interested in are:
- ability to "wrap" a remote API in a regular Clojure function
- abstraction away from the details of how the API is implem
