Thanks! Great idea, posted!
On Fri, Dec 13, 2013 at 11:08 AM, Philipp Meier phme...@gmail.com wrote:
Hi,
Am Donnerstag, 12. Dezember 2013 18:54:03 UTC+1 schrieb Alex P:
We (Munich Lambda[1]) are organising Meetups, dedicated to Functional
Programming, and Clojure specifically.
I
@Cesar
I've made a little advancement on dynamic encoding/decoding, here's a gist
with a proof of concept: https://gist.github.com/ifesdjeen/7902409
On Wed, Dec 4, 2013 at 8:28 AM, Cesar Canassa cesar.cana...@gmail.comwrote:
Hi,
I see that the repeated-type requires a constant repeat count.
I've added 32-bits based bit type to Buffy:
https://github.com/clojurewerkz/buffy#bit-type
Does it suit your needs? If not, what length of bits do you require?
On Wed, Dec 4, 2013 at 3:58 PM, Rob Day robert@merton.oxon.org wrote:
On 29 November 2013 22:15, Alex P
I've added a missing option for wrapped buffers:
https://github.com/clojurewerkz/buffy#buffer-types
On Wed, Dec 4, 2013 at 9:28 AM, Ulises ulises.cerv...@gmail.com wrote:
While we're on the subject, I found no way of decoding/interpreting an
already existing sequence (ByteBuffer) of bytes,
@Rob
I have a working prototype of bits, which are encoded from 32 flags and
decoded back to them. I've added a couple of helper methods such as
`set-bits-at` and `get-set-bits` and so on to facilitate it.
Although I recommend using enums for that (which is possible in majority of
cases).
I'll
@Thomas, let me know if you run into any problems. Since the project is
quite young, I'm very open to add a couple of features. Rob, Ulisses and
Cesar have done a very nice job providing some very nice ideas!
On Sat, Dec 7, 2013 at 12:05 AM, Oleksandr Petrov
oleksandr.pet...@gmail.com wrote
In ClojureWerkz[1], there're some projects, for example, Titan[2]. Zach
Maril [3] is taking care of them, mostly.
[1] http://clojurewerkz.org
[2] https://github.com/clojurewerkz/titanium
[3] https://twitter.com/zackmaril
On Mon, Dec 2, 2013 at 3:01 PM, Paweł Rozynek pro...@gmail.com wrote:
Forgot to mention, Zweikopf comes as a Ruby gem and as a Clojure library.
You should make a decision though wether you're running Ruby scripting
container from Clojure or start Clojure runtime from Ruby...
On Mon, Sep 9, 2013 at 5:50 PM, Oleksandr Petrov oleksandr.pet...@gmail.com
wrote:
I've
I've been working with an application that written in Ruby and Clojure.
Nothing forbids you from using some messaging system for communication
between Ruby and Clj, although we required direct access to Ruby from
Clojure and vice versa.
That's pretty much how Zweikopf was born:
It looks all fine to me,
Here's a repo where i've put Enlive, Ring and Compojure together :
https://github.com/ifesdjeen/enlive-ring
You can run it using ring: https://github.com/weavejester/lein-ring
Let me know if it works for you, otherwise would you mind to push code
somewhere in a gist on
We're using Clojure code for configuration.
In essence, it looks pretty much like:
https://gist.github.com/ifesdjeen/440320a52f4edeedfd1a
And you can run it as:
lein run --config config/development.clj
On Sun, Sep 8, 2013 at 10:07 PM, Gordon Stratton
gordon.strat...@gmail.comwrote:
James,
RingBuffer operates in it's own pool, adding notifications blocks
RingBuffer's yielding, therefore makes notify function block eternally.
New version containing a bugfix for that problem, together with throughput
tests was added and pushed to Clojars:
[clojurewerkz/eep 1.0.0-alpha4]
Please
Cassaforte [1] is a Clojure client for Apache Cassandra 1.2+. It is built
around CQL 3
and focuses on ease of use. You will likely find that using Cassandra from
Clojure has
never been so easy.
1.2.0 is a minor release that introduces one minor feature, fixes a couple
of bugs, and
makes
EEP [1], Clojure Embedded Event Processing library 1.0.0-apha4 is released.
EEP is c library for lightweight embedded event processing, it combines a
lightweight
generic event handling system, multiple windowed stream operations,
aggregations
and multiple buffer types.
New release contains
EEP is an appropriate choice when:
* you have to do processing on a single machine, or can split processing
to several machines using downstreams which will forward processing from
end-observer to emitter on a different machine
* if you want it to be very fast and want to have pluggable
It actually doesn't do anything Clout does.
Latest modifications actually make it 100% complementary to clout, so now
you can do:
(defroute about /about)(defroute documents /docs/:title)
(compojure/defroutes main-routes
(compojure/GET about-template request (handlers.root/root-page
request))
We're using that technique for both long-running server processes and small
web applications, i've covered in a blog post some time ago:
http://coffeenco.de/articles/how_to_deploy_clojure_code.html
Basically, create a jar and run it from a jar.
If you don't want to embed jetty, you can deploy to
17 matches
Mail list logo
