On 15/01/2015 12:37, Christian Weilbach wrote:
I am not sure whether I understand your problem correctly, but if the
js callback API guarantees transactional safety around your queries,
then you cannot use core.async internally, but only expose channels to
the outside. I have done the same thing for IndexedDB, core.async
didn't work, because the callbacks are basically transformed to the
heap and the actual transaction is over when the channel operations
continue (because it is closed with the stack in case of IndexedDB).
https://github.com/ghubber/konserve/blob/master/src/cljs/konserve/indexeddb.cljs
Btw. if the konserve kv-protocol fits your needs feel free to
implement it ;-).
Cheers,
Christian
The reason I asked is because in a previous thread - "Clojurescript on
NodeJS clarification" - I asked:
2. Callback hell
Does Clojurescript help to alleviate NodeJS callback hell or just
sweeten the syntax?
... to which David Nolen replied:
Yes see core.async.
I'm assuming by this we can substitute core.async for typical NodeJS
nested callbacks but I'm no expert so .....
gvim
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups "ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.
