Alan,
Thanks for your reply. I was also looking for a RPC mechanism, and I looked
at castra from the hoplon stack.
One thing that is turning me off is that I will have to define my api as
special 'defn', instead of regular defns. I have used shoreleave / fetch
before and have liked their simp
Hi Murtaza, the primary motivation of cljson is to improve browser
deserialization performance when the client is ClojureScript and the server
is Clojure. You can start with EDN and easily move to cljson if
client-side deserialization becomes your bottleneck.
Alan
On Monday, January 13, 2014
Alan,
I am exploring what option to use for exchanging data between my server and
client. EDN and Cljson are two of the options. What are the pros / cons of
using cljson over edn ?
What was the motive in creating this library ?
Thanks,
Murtaza
On Tuesday, June 25, 2013 12:58:11 AM UTC+5:30, A
Glad you enjoy! And yes, totally into the cljson->clj [map data] arity.
Alan
On Monday, June 24, 2013 1:50:00 PM UTC-4, Thomas Heller wrote:
>
> Hey,
>
> this looks pretty sweet! I stuck with EDN for now but its way too slow, so
> I'm gonna give this a shot.
>
> One thing: I'm don't think its th
Hey,
this looks pretty sweet! I stuck with EDN for now but its way too slow, so
I'm gonna give this a shot.
One thing: I'm don't think its the best idea to fall back to
*default-data-readers*, would you be open to adding a second argument to
'cljson->clj which takes a map specifying readers? e
Hi all,
I'm pleased to announce the release of cljson 1.0.0, a Clojure and
ClojureScript data serialization library designed for maximal Clojure data
deserialization speed in the browser:
https://github.com/tailrecursion/cljson. cljson was designed to take
advantage of the native JSON parsing
