Didier wrote on Friday, January 22, 2016 at 12:51 PM:
Like I said, if the features planned for Clojure can actually be implemented on
an older JVM, I think that's fantastic and it should be done so.
And it has been done. We’ve continued to see Clojure grow as a language and as
an ecosystem witho
Yes +1 to qsys, such a library would be quite useful and enable using
Clojure in additional enterprise settings.
Regards,
Timur
On Saturday, January 23, 2016 at 9:50:45 PM UTC+1, qsys wrote:
>
> True, hazelcast, or JGroups, in vertx 3 for clustering/autodiscovery. It
> may be 'easy' to imple
True, hazelcast, or JGroups, in vertx 3 for clustering/autodiscovery. It
may be 'easy' to implement, but it has been quite nicely wrapped, together
with netty messaging (not only pub-sub) in vert.x, having connectors to
'pure TCP', websockets etc. I have been thinking of doing something similar
On Jan 23, 2016 11:36 AM, "Harold" wrote:
>
> Hello,
>
> While destructuring yesterday, I encountered this difference:
>
> > (let [{:keys [:a :b]} '(:a 1 :b 2)] [a b])
> [1 2]
>
> > (let [{:keys [:a :b]} [:a 1 :b 2]] [a b])
> [nil nil]
>
> I have read some of the relevant documentation and some re
+1 to what Andrey said.
You could also run Redis as a backend and use it's pubsub service [1], if
being more language agnostic is more your thing.
Depending on where you are hosting, you could also use a hosted pubsub
mechanism, such as Google Cloud PubSub[2] or AWS SNS[3].
There are definitely
that's an implementation detail you should not rely on.
it only works to support keyword arguments to functions
On 23 Jan 2016 17:36, "Harold" wrote:
> Hello,
>
> While destructuring yesterday, I encountered this difference:
>
> > (let [{:keys [:a :b]} '(:a 1 :b 2)] [a b])
> [1 2]
>
> > (let [{:k
Hello,
While destructuring yesterday, I encountered this difference:
> (let [{:keys [:a :b]} '(:a 1 :b 2)] [a b])
[1 2]
> (let [{:keys [:a :b]} [:a 1 :b 2]] [a b])
[nil nil]
I have read some of the relevant documentation and some related blog posts,
but I am still having trouble explaining thi
The eventbus of vert.x as far as I know is implemented on top of
hazelcast[1] that you already can use from clojure.
Make a eventbus like concept on top of hazelcast is pretty easy and it
already gives you the autodiscovery and all the "clustering" stuff for free.
[1]; http://hazelcast.org/use-ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22.01.2016 20:35, Teemu Kaukoranta wrote:
> On Friday, 22 January 2016 20:53:25 UTC+2, Christian Weilbach
> wrote:
>
>>
There's two things that make this difficult to understand:
its academic nature, and the fact that many of us are just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.01.2016 05:11, Christopher Small wrote:
> Can you listen for changes on a server store?
What exactly do you want to do? If you want to track updates to a
CRDT, I would create a stage and subscribe to the updates as I do in
the topiq client:
htt
Hi everyone,
This is a small testing library inspired by midje. Before you start
pulling your hair, about why do we need yet another unit-testing
library, please consider reading the README and/or intro.md.
https://github.com/jimpil/fudje
TL/DR;
Midje comes with some very cool features but
Depends on what you want... what I really like is the easy modularity:
deploy new 'verticles' somewhere in your network, and they're just all
connected through a the eventbus. I make a 'new' module, I put it somewhere
and it's automatically picked up by the appication and I can communicate
with
12 matches
Mail list logo
