Re: difference between first & peek; rest & pop

ng else to rely on). first, rest, next and conj are part of the sequence abstraction; use them when you're logically manipulating a sequence. peek, pop and conj can be part of either the stack abstraction (if used on lists or vectors) or the queue abstraction (if used on persistent queues).

Re: difference between first & peek; rest & pop

first and rest are defined in terms of position, and work on anything that can be treated as an ordered collection peek and pop work in terms of "natural insertion order" and only work with things that behave like a stack - (so not lazy-seqs, strings, etc.) lists push and pop from

Re: difference between first & peek; rest & pop

Also, pop throws an exception on the empty list whereas rest returns (). On Thursday, May 30, 2013 at 12:43:14 AM UTC-4, Seven Hong wrote: > > Hi all, > > Could some one explain what's the difference between first and peek, rest > and pop? For me it looks like they be

Cosla: Clojure tool for SLA metrics via JIRA Rest API

Greetings, I've open sourced a command-line tool I wrote, in Clojure, for pulling SLA (service-level agreement) stats from JIRA using the JIRA Rest API. https://github.com/noahlz/cosla Given a JIRA instance, it can generate some CSV files reporting on the issues matching a JQL you pr

[ANN] Bidirectional Ring router. REST oriented. Rails inspired.

https://github.com/darkleaf/router -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe

Re: clojure.spec and the rest of clojure

Hi For your first question, have a look at this thread: https://groups.google.com/forum/#!topic/clojure/d_3V9MfLZmY - Patrick On Monday, June 13, 2016 at 8:18:30 AM UTC+2, Philip Markgraf wrote: > > Rich's session on the Cognicast brought up interesting questions for me. > > - Is Clojure.spec b

clojure.spec and the rest of clojure

Rich's session on the Cognicast brought up interesting questions for me. - Is Clojure.spec being applied within clojure.core and other parts of the language? - Has the test.check capability led to the discovery of bugs in clojure.core and other parts of the language? - Does anyone (else) antici

Re: Ted Dziuba: The S in REST

, Patrick Kristiansen wrote: > > Hi everyone > > Has anyone read and given any thoughts to the ideas about immutability and > REST by Ted Dizuba here: > > http://teddziuba.github.io/2014/08/18/the-s-in-rest/ > > Has anyone done anything resembling this? I think the

Any clojure test frameworks support jsonPath macters like rest-assured in java?

Hi hivemind, In Java, we have > get("/lotto").then().assertThat().body("lotto.winners.winnerId", hasItems(23, > 54)); > > Any test frameworks can support this like below? (deftest should-return-200j (testing "should return 200 ok" (let [{body :body} (my-app (mock/request :get "/"))]

Re: Ted Dziuba: The S in REST

Shameless (but very relevant) plug: come check out my talk at Clojure/conj! http://clojure-conj.org/speakers#bcalderwood On Wednesday, October 14, 2015 at 7:25:35 AM UTC-4, Patrick Kristiansen wrote: > > On Wednesday, October 14, 2015 at 5:49:06 AM UTC+2, James Reeves wrote: >> >> Of course, the

Re: Ted Dziuba: The S in REST

On Wednesday, October 14, 2015 at 5:49:06 AM UTC+2, James Reeves wrote: > > Of course, the difficulty with this architecture is that few databases > have fast, immutable snapshots built in, so you'd have to get a little > creative with your database design. > Which, I guess, is where Datomic wou

Re: Ted Dziuba: The S in REST

istiansen <mailto:patr...@patrkris.dk>> wrote: > Has anyone read and given any thoughts to the ideas about immutability and > REST by Ted Dizuba here: > > http://teddziuba.github.io/2014/08/18/the-s-in-rest/ > <http://teddziuba.github.io/2014/08/18/the-s-in-rest/> > >

Re: Ted Dziuba: The S in REST

On 13 October 2015 at 09:49, Patrick Kristiansen wrote: > > Has anyone read and given any thoughts to the ideas about immutability and > REST by Ted Dizuba here: > > http://teddziuba.github.io/2014/08/18/the-s-in-rest/ > > Has anyone done anything resembling this? I t

Re: Ted Dziuba: The S in REST

The thought that came to my mind when reading it was something like, "Hasn't anybody heard of MVCC?" -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are mod

Ted Dziuba: The S in REST

Hi everyone Has anyone read and given any thoughts to the ideas about immutability and REST by Ted Dizuba here: http://teddziuba.github.io/2014/08/18/the-s-in-rest/ Has anyone done anything resembling this? I think the ideas sounds intriguing. Best regards, Patrick -- You received this

Re: Writing REST api the right way

based modules. Although the initial purpose >>> of picking the language was to do some CPU demand calculations and data >>> processing, I found it really simple yet enjoyable to write REST api as >>> well (we also use Node.js and Elixir for that purpose and it works prett

Re: Writing REST api the right way

services, I thought I am >> gonna make one or two Clojure based modules. Although the initial purpose >> of picking the language was to do some CPU demand calculations and data >> processing, I found it really simple yet enjoyable to write REST api as >> well (we also use Nod

Re: Writing REST api the right way

icking the language was to do some CPU demand calculations and data > processing, I found it really simple yet enjoyable to write REST api as > well (we also use Node.js and Elixir for that purpose and it works pretty > well - especially with Elixir thanks to awesome yet simple Erlang model

Re: Writing REST api the right way

; especially thanks to the failover built-in. It also greatly shows how > Clojure can reduce the `Java boilerplate`. > > Speaking on the performance note, I am not entirely sure what's causing my > REST API to be slower than `Node.js` one, I have two the same auth logic >

Re: Writing REST api the right way

> That would apply to common actions like typing and entering. Login being > slower than that isn't likely to be as much of a bother as you likely only > do it infrequently, maybe as much as once a day if you're paranoid and clear > cookies nightly. Yeah, to me that is the sort of reasoning that l

Re: Writing REST api the right way

On Wednesday, June 24, 2015 at 6:37:14 PM UTC-4, raould wrote: > > > 350ms sounds fast enough for a low-frequency user interaction. In fact, > once > > login is fast enough not to annoy your users, you don't *want* any more > > speed from it, as further speedup then only benefits blackhats tryin

Re: Writing REST api the right way

> 350ms sounds fast enough for a low-frequency user interaction. In fact, once > login is fast enough not to annoy your users, you don't *want* any more > speed from it, as further speedup then only benefits blackhats trying to > brute-force one of your users' accounts. So, it might be a feature, n

Re: Writing REST api the right way

king on the performance note, I am not entirely sure what's causing my > REST API to be slower than `Node.js` one, I have two the same auth logic > implemented in both Node/Clojure. The Node.js version is running on Heroku > (London) with MongoLab hosted in (US-east-1) which can h

Re: Writing REST api the right way

Thanks for the reference, I've seen it before and it looks interesting, especially thanks to the failover built-in. It also greatly shows how Clojure can reduce the `Java boilerplate`. Speaking on the performance note, I am not entirely sure what's causing my REST API to be s

Re: Writing REST api the right way

On Tuesday, June 23, 2015, Mike Grabowski wrote: > ... I just can't stop thinking about non-blocking evented > IO interactions. It just does not feel right to me to > block the thread when e.g. logging in an user. > Unfortunately, there are no NIO drivers for the database > engines I am interested

Re: Writing REST api the right way

ugh the initial purpose > of picking the language was to do some CPU demand calculations and data > processing, I found it really simple yet enjoyable to write REST api as > well (we also use Node.js and Elixir for that purpose and it works pretty > well - especially with Elixir

Re: Writing REST api the right way

I thought I am > gonna make one or two Clojure based modules. Although the initial purpose > of picking the language was to do some CPU demand calculations and data > processing, I found it really simple yet enjoyable to write REST api as > well (we also use Node.js and Elixir for that

Writing REST api the right way

purpose of picking the language was to do some CPU demand calculations and data processing, I found it really simple yet enjoyable to write REST api as well (we also use Node.js and Elixir for that purpose and it works pretty well - especially with Elixir thanks to awesome yet simple Erlang model

[ANN] yada 0.4.0 - async REST web library

yada is a library for creating RESTful Ring handlers, similar(ish) to Liberator. The main difference is that yada fully supports async operation (provided by Zach Tellman's manifold library). It is a kind of reactive Clojure-based response to Java's ratpack.io or Scala's spray.io. yada is desig

Re: [ANN] Sweet Liberty: Set Your Data Free with Clojure and REST

m/2015/02/15/sweet-liberty-set-your-data-free-with-clojure-and-rest/ >> >> >> Sweet-Liberty is a library for building database-backed RESTful services >> using Clojure. You can think of it as a means to build and configure >> components that translate between REST

Re: [ANN] Sweet Liberty: Set Your Data Free with Clojure and REST

On Tuesday, February 17, 2015 at 11:24:48 AM UTC-5, Bill Piel wrote: > > Blog post: > https://blog.rjmetrics.com/2015/02/15/sweet-liberty-set-your-data-free-with-clojure-and-rest/ > > > Sweet-Liberty is a library for building database-backed RESTful services > using Cloj

Re: Library (or libraries) for translating REST queries to database queries?

Sooo.. it's been a while, but my team finally got around to open sourcing the library we've built to address this need. We've been using it for several months with much success. Github repo is here: https://github.com/RJMetrics/sweet-liberty/ On Tuesday, September 24, 2013 at 9:35:38 AM UTC-4,

[ANN] Sweet Liberty: Set Your Data Free with Clojure and REST

Blog post: https://blog.rjmetrics.com/2015/02/15/sweet-liberty-set-your-data-free-with-clojure-and-rest/ Sweet-Liberty is a library for building database-backed RESTful services using Clojure. You can think of it as a means to build and configure components that translate between REST and SQL

"rest" arguments and desctructuring / nil vs. empty

For "rest" arguments, as in (defn foo [x & r] r), when the remaining arguments are rolled up into a sequence, you will get nil instead of an empty sequence. Is it fair to say that the "rest" nomenclature came about back at the beginning of Clojure, when rest really did

Bind and destructure rest param as map

Hi all, I've got a couple questions regarding rest parameters. 1) In function params, is there a way to destructure the rest argument as a map and bind it to a name at once in the function signature? Below is an example. f1 takes opts parameter. Now I have f2 with similar signature

Re: Advice for building backend REST services from scratch using clojure

I felt the Austin pain. Then I discovered figwheel. In one fell swoop, it solved all aforementioned problems. Live coding with Emacs has never been more joyful. https://github.com/bhauman/lein-figwheel On Tuesday, October 7, 2014 7:21:19 PM UTC+3, g vim wrote: > > On 11/04/2014 09:17, Colin Yate

Re: Advice for building backend REST services from scratch using clojure

To be fair, Cursive doesn't yet provide a great CLJS REPL solution either, although that is coming soon. Right now, for ease of getting a CLJS REPL up and running Light Table definitely wins. On 8 October 2014 05:20, gvim wrote: > On 11/04/2014 09:17, Colin Yates wrote: > >> * you can fight it

Re: Advice for building backend REST services from scratch using clojure

On 11/04/2014 09:17, Colin Yates wrote: * you can fight it as hard as you like but you will eventually end up using emacs, clojure-mode, cider, paredit and magit and then wonder how you ever lived without it, but not without spending at least a month or two cursing anything to do wi

Re: Advice for building backend REST services from scratch using clojure

On 11/04/2014 09:17, Colin Yates wrote: * you can fight it as hard as you like but you will eventually end up using emacs, clojure-mode, cider, paredit and magit and then wonder how you ever lived without it, but not without spending at least a month or two cursing anything to do wi

Re: Advice for building backend REST services from scratch using clojure

With Lispy languages, you can do whatever you want without worrying too much about underlying web server, db, etc. I use my own constructors like: (define-crud-handler :employee [:path ["customers" cust-id "sites" site-id "employees"] :auth-required? true] {:collection {:create (employees-cr

Re: Advice for building backend REST services from scratch using clojure

With Lispy languages, you can do whatever you want without worrying too much about underlying web server, db, etc. I use my own constructors like: (define-crud-handler :employee [:path ["customers" cust-id "sites" site-id "employees"] :auth-required? true] {:collection {:create (employees-cr

Re: Advice for building backend REST services from scratch using clojure

Hey Colin - thanks for the kind words! And I must apologise for my last previous comment too - I actually meant to come back and do so but didn't for whatever reason. It was one of those comments that sounded better in my head than when I saw it written down later - I'm sorry about that. I'm sure y

Re: Advice for building backend REST services from scratch using clojure

Just FYI - I got a new laptop and thought I would give it another look-see. Consider me impressed. I maybe didn't spend enough time with it, but a lot of the rough edges have been smoothed out, the performance seems to have increased, it is just a really nice place to be. To be clear, emacs roc

Re: Best method for REST api authentication?

Ok, I was confused, the solution for this is just to use a session - if the authentication is done using a cookie the server is basically stateless, which would comply to REST. I implemented cookie store session following this tutorial: http://vijaykiran.com/2012/02/web-application-development

Best method for REST api authentication?

Hi, I'm new to Clojure and have little experience with api development. I'm looking for a way to implement REST api authentication. As far I understand, the best way to do this is using an authentication token. The goal is use this for mobile apps. I would prefer to avoid sending

Re: Advice for building backend REST services from scratch using clojure

Prismatic Schema is awesome for describing the (web) apis, does also validations & coersion. Using it in all web projects nowadays. If you are thinking of json apis, swagger is a great tool to publish out the documentation. For clojure at least these schema / swagger-aware web libs do exist: S

Re: Advice for building backend REST services from scratch using clojure

Play around with this: $ lein new compojure myapp $ cd myapp $ lein ring server-headless Started server on port 3000 On Thursday, April 10, 2014 9:13:19 AM UTC-5, Kashyap CK wrote: > > Hi, > I have the opportunity to build a set of services from scratch. I plan to > use clojure

Re: Advice for building backend REST services from scratch using clojure

You should take a look at Liberator<http://clojure-liberator.github.io/liberator/> for the REST services. We're using it at Ardoq <http://ardoq.com> to build our REST-APIs and we are very happy with it. kl. 16:13:19 UTC+2 torsdag 10. april 2014 skrev Kashyap CK følgende: >

Re: Advice for building backend REST services from scratch using clojure

No worries, I didn't think what you wrote was inflammatory and it's undeniable that Emacs has the largest mindshare in the Clojure world. But the alternatives are getting better and better and I think I could make a reasonable case that Cursive is better than Emacs for some circumstances and/or pro

Re: Advice for building backend REST services from scratch using clojure

My two cents... Ring/Compojure, Friend, Datomic. I've had these in production since 2012, no issues really and its still fun to hack on them. On Thursday, 10 April 2014 15:13:19 UTC+1, Kashyap CK wrote: > > Hi, > I have the opportunity to build a set of services from scratch. I plan to > use c

Re: Advice for building backend REST services from scratch using clojure

Colin - you are right - I shouldn't throw out such inflammatory marks, particularly when they do a disservice to the excellent work done in Cursive Clojure, Lighttable and Counter Clockwise (and others that I am not aware off). For me personally, after years of using Eclipse then IntelliJ and (

Re: Advice for building backend REST services from scratch using clojure

Ah, ok - if you're already using Emacs then have at it :-) On 11 April 2014 21:32, C K Kashyap wrote: > Just for the record ... I am an emacs fan :) > Had been a vim power user for a long time but switched to emacs after the > fp bug bit me. > Regards, > Kashyap > > > On Fri, Apr 11, 2014 at 2:

Re: Advice for building backend REST services from scratch using clojure

Just for the record ... I am an emacs fan :) Had been a vim power user for a long time but switched to emacs after the fp bug bit me. Regards, Kashyap On Fri, Apr 11, 2014 at 2:50 PM, Colin Fleming wrote: > you can fight it as hard as you like but you will eventually end up using >> emacs, cloju

Re: Advice for building backend REST services from scratch using clojure

> > you can fight it as hard as you like but you will eventually end up using > emacs, clojure-mode, cider, paredit and magit and then wonder how you ever > lived without it, but not without spending at least a month or two cursing > anything to do with emacs :). > As the developer of Cursive, I'd

Re: Advice for building backend REST services from scratch using clojure

As others have said - a more focused question would help. Our back end runs on ring + compojure using https://github.com/jkk/honeysql for querying and straight https://github.com/clojure/java.jdbc for writes. We use https://github.com/marick/Midje/wiki rather than clojure.test and https://gith

Re: Advice for building backend REST services from scratch using clojure

ata (clients exist for JDBC and almost all noSQL > stores) > > The above is fine if "REST" in your case translates to "CRUD + some > querying." If you want to design a more thorough and careful REST > architecture, Liberator will probably be of interest. > &

Re: Advice for building backend REST services from scratch using clojure

ents exist for JDBC and almost all noSQL stores) The above is fine if "REST" in your case translates to "CRUD + some querying." If you want to design a more thorough and careful REST architecture, Liberator will probably be of interest. If you know your service will need

Re: Advice for building backend REST services from scratch using clojure

Look into: https://github.com/pedestal/pedestal http://www.datomic.com/ On Thursday, 10 April 2014 07:13:19 UTC-7, Kashyap CK wrote: > > Hi, > I have the opportunity to build a set of services from scratch. I plan to > use clojure for this. > I'd like to experiment with options available out ther

Advice for building backend REST services from scratch using clojure

Hi, I have the opportunity to build a set of services from scratch. I plan to use clojure for this. I'd like to experiment with options available out there - options such as - what webserver, what database etc. I'd like it very much if you could share some of your experiences in this and possibl

Re: Adding query customization to Ring-based REST APIs

That's a great point of reference, thanks for the tip. I'm in the market mostly for bits and pieces that I can stitch onto my project, so something like service-hub-examples is a great way to see how it's used. I haven't used protocols much, your project seems like a pretty good fit for them. On

Re: Adding query customization to Ring-based REST APIs

Hello Alexander, I did some work in this area some time ago, and the result was service-hub library - created to simplify basic CRUD services. It's designed to allow more then one type of data-store, currently it supports SQL databases (i use my own fork

Adding query customization to Ring-based REST APIs

I'm investigating adding query options to my Ring app's GET requests for the more boring CRUD routes. I'd like to allow the caller to specify a set of SQL-level query customizations such as sorting, paging, counting, distinct ons, limits, some basic constraints etc. across all of my resources, ide

Re: Doubt about "Destructuring rest sequences as map key/value pairs"

No problem. On Mon, Sep 30, 2013 at 9:11 AM, Daniel Meneses wrote: > thanks !! > > > On Saturday, September 28, 2013 9:57:13 PM UTC-3, Ambrose > Bonnaire-Sergeant wrote: > >> The or syntax should be {lastname "Meneses"} >> >> Thanks, >> Ambrose >> >> >> On Sun, Sep 29, 2013 at 8:54 AM, Daniel M

Re: Doubt about "Destructuring rest sequences as map key/value pairs"

thanks !! On Saturday, September 28, 2013 9:57:13 PM UTC-3, Ambrose Bonnaire-Sergeant wrote: > > The or syntax should be {lastname "Meneses"} > > Thanks, > Ambrose > > > On Sun, Sep 29, 2013 at 8:54 AM, Daniel Meneses Báez > > > wrote: > >> I think that the second and third lines in the followi

Re: Doubt about "Destructuring rest sequences as map key/value pairs"

The or syntax should be {lastname "Meneses"} Thanks, Ambrose On Sun, Sep 29, 2013 at 8:54 AM, Daniel Meneses Báez wrote: > I think that the second and third lines in the following example should > yield the same output... > > *user=> (defn my-name [& {:keys [name lastname] :or {:lastname > "Men

Doubt about "Destructuring rest sequences as map key/value pairs"

I think that the second and third lines in the following example should yield the same output... *user=> (defn my-name [& {:keys [name lastname] :or {:lastname "Meneses"}}] (str name " " lastname))* *#'user/my-name* *user=> (my-name :name "Daniel" :lastname "Meneses")* *"Daniel Meneses"* *user=> (

Re: Library (or libraries) for translating REST queries to database queries?

I took it as a challenge, so i made this tiny library to play with: https://github.com/sebastiansen/mummy Adios amigo On Tuesday, September 24, 2013 10:35:38 AM UTC-3, Bill Piel wrote: > > I want to use clojure to build a web service with a RESTful API that > exposes resources stored in a relat

Re: Library (or libraries) for translating REST queries to database queries?

Hi Bill, Did you look at restSQL? http://restsql.org For custom needs generating SQL from REST routes might be a way. Shantanu On Tuesday, 24 September 2013 19:05:38 UTC+5:30, Bill Piel wrote: > > I want to use clojure to build a web service with a RESTful API that > exposes resourc

Re: Library (or libraries) for translating REST queries to database queries?

U... OData maybe a bit overwhelming, but I guess it is in your direction http://www.odata.org/ There is an implementation in Java https://code.google.com/p/odata4j/ (apparently with consumers and producers, too) There is an experimental Clojure project consuming odata4j https://github.com/da

Library (or libraries) for translating REST queries to database queries?

I want to use clojure to build a web service with a RESTful API that exposes resources stored in a relational database (mysql in this case). I'd like to use a library that, given a specification of the db schema, would translate incoming requests to db queries, or korma constructs. Examples m

Re: [ANN] REST in Peace 0.1.0

Link to repository https://github.com/sebastiansen/rip On Friday, July 19, 2013 7:03:18 PM UTC-4, Sebastian Rojas wrote: > > A library for RESTFul applications built on top of Compojure, includes > routing abstractions with reverse routing functionalities and validation > helpers. -- -- You r

Re: [ANN] REST in Peace 0.1.0

On Saturday, July 20, 2013 3:21:47 AM UTC+2, Steven Degutis wrote: > > https://github.com/sebastiansen/rip > > Thanks ! I'll be implementing RESTful ws this summer and intended to use http://clojure-liberator.github.io/liberator/ . How does your library compares to it ? Any advice on how to ma

[ANN] REST in Peace 0.1.0

A library for RESTFul applications built on top of Compojure, includes routing abstractions with reverse routing functionalities and validation helpers. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure

Re: [ANN] REST in Peace 0.1.0

https://github.com/sebastiansen/rip On Fri, Jul 19, 2013 at 7:49 PM, Jeremy Heiler wrote: > Got a link? > > On July 19, 2013 at 8:37:13 PM, Sebastian Rojas ( > sebastian.rojas.viva...@gmail.com) wrote: > > A library for RESTFul applications built on top of Compojure, includes > routing abstracti

Re: [ANN] REST in Peace 0.1.0

Got a link? On July 19, 2013 at 8:37:13 PM, Sebastian Rojas (sebastian.rojas.viva...@gmail.com) wrote: A library for RESTFul applications built on top of Compojure, includes routing abstractions with reverse routing functionalities and validation helpers. -- -- You received this message bec

Re: difference between first & peek; rest & pop

They are equivalent when operating on lists, but not so when operating on vectors (peek = constant time last, pop = log time remove last element) or queues (peek = first, pop = remove first element returning a queue -- rest/next would return a seq). Also, they refuse to work with non-list

difference between first & peek; rest & pop

Hi all, Could some one explain what's the difference between first and peek, rest and pop? For me it looks like they behave exactly same on sequences.. Thanks! Best, Seven Hong -- -- You received this message because you are subscribed to the Google Groups "Clojure" group.

Re: growing a rest json/xml api

ou point me out best practices/libraries to make a rest api with > ring with json/xml output depending on "Accepts" request header? > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email

growing a rest json/xml api

Hi, can you point me out best practices/libraries to make a rest api with ring with json/xml output depending on "Accepts" request header? -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, s

Re: Full stack Clojure web/REST framework - is there any mileage in it?

I'm a bit curious. My immediate reaction was to ask what you use instead of Spring (none?), Hibernate (datomic?) and what did you use to provide the plumbing for web apps (assuming you needed it and didn't just write it all from scratch). My second thought was then what is the difference betwee

Re: Full stack Clojure web/REST framework - is there any mileage in it?

Hello all! First i would like to mention that I'm very new to Clojure, and still learning the language/functional programming. Mostly I'm doing web stuff, with the usual suspects (php,ruby,python) and im usually using a framework for RAD development. Frameworks as they are usually implemented

Consuming REST APIs in Clojure: What's the best way?

Hi, I'm using clj-http to consume a JSON REST API. The code is ugly [1]: I'm in the process of rewriting it, and I would love to have some inputs from the community on how to design it. I love the Datomic way "everything is data", but I don't want/can re-invent a qu

Re: Building a REST API / efficient RPC interface in Clojure

On Monday, February 11, 2013 2:48:30 AM UTC+1, Mikera wrote: > > Thanks bernardH - these are great links, probably pretty close to what I > was looking for. > > Will try some experiments with these over the next few days. > Hi, I, for one, would be interested by the results of those experiments

Re: Building a REST API / efficient RPC interface in Clojure

key [**]. Would you consider including this possibility in your lein > template (which I'd very much like to use, considering the quality of your > http-kit !) > > As for REST, have you considered liberator [***] ? > > Cheers, > > Bernard > > [*] https://gi

Re: Building a REST API / efficient RPC interface in Clojure

> > Define an API in terms of messages > I'm not familiar with the concept - just out of curiosity, what does a mesagge-based API consist of? Is the drastically different from most REST/JSON web APIs out there? Thank you - Victor -- -- You received this message because you

Re: Building a REST API / efficient RPC interface in Clojure

d by Rich Hickey [**]. Would you consider including this possibility in your lein template (which I'd very much like to use, considering the quality of your http-kit !) As for REST, have you considered liberator [***] ? Cheers, Bernard [*] https://github.com/Datomic/fressian [**] http://skill

Re: Building a REST API / efficient RPC interface in Clojure

- Also maintain a mapping between the API and handler functions that get > called in response to receiving a message > - Expose the API as a general purpose REST API for the web > - Also expose the same API using some form of efficient binary > serialisation for RPC usage > >

Building a REST API / efficient RPC interface in Clojure

ain a mapping between the API and handler functions that get called in response to receiving a message - Expose the API as a general purpose REST API for the web - Also expose the same API using some form of efficient binary serialisation for RPC usage FWIW, the objective is make the same API avai

Re: Full stack Clojure web/REST framework - is there any mileage in it?

I've been giving a lot of thought to frameworks and tempates lately, so I'll share my thoughts. The goal of frameworks and templates, in my mind, is repeatable assembly. Small, focused libraries don't get in the way of that design goal. Frameworks and templates sit on top of the language. W

Re: Full stack Clojure web/REST framework - is there any mileage in it?

Let me add a couple more thoughts. I hung out on the TurboGears project a few years ago because I thought they were heading in a good direction. They use templating engines (Genshi), and I like that idea. One framework; many templates. They also made a major redesign decision mid stream, so

Re: Full stack Clojure web/REST framework - is there any mileage in it?

I think there is value, but we as a community are not yet ready for it. The problem is that the "full stack" endgoal is itself shifting in definition, towards single-page apps. There is not much appetite for the creation of a RoR clone, when the landscape in which RoR was created has shifted so m

Re: Full stack Clojure web/REST framework - is there any mileage in it?

+1, excellent summary of the key points. We got rid of Spring, Hibernate et cie for the same reasons. They were somewhat needed in Java but in Clojure we found that they were cumbersome to use and brought little value. We realized along the way that some generated Java code (Hibernate is a good

Re: Full stack Clojure web/REST framework - is there any mileage in it?

Great points. Also take RoR as an example: ruby, dynamic as it may be, still relies on the notion of a class as code owner which means that the class is the namespacing unit for all code that wants to participate in operating on a specific data structure, such as a hash or array. After 20-30 y

Re: Full stack Clojure web/REST framework - is there any mileage in it?

The Clojure tradition of mixing-and-matching small libraries rather than relying on large frameworks like Spring did not emerge by accident. The Java language itself causes library authors to create their own types thereby creating an impedance mismatch with other libraries. Spring (and similar

Re: Full stack Clojure web/REST framework - is there any mileage in it?

Hi Clojures, I'm new and thought I'd chime in. :-) I've been playing with Clojure for a few weeks, built a quick Markov Chain Generator and started rebuilding my blog with Compojure. I think there's a philosophical bent in the Clojure community toward > small,

Re: Full stack Clojure web/REST framework - is there any mileage in it?

On Friday, January 11, 2013 4:33:15 PM UTC-5, Eric MacAdie wrote: > > Is there a page that gives "Clojure web recipes"? It would be great for > beginners if you could have one place that says "To make a web app, you > need X, Y and Z, and here are libraries that fulfil each of these needs." > Ma

Re: Full stack Clojure web/REST framework - is there any mileage in it?

A good thought/discussion provoking post, thanks. I find myself between two camps here. On one side and coming from the position of both learning Clojure and coming back to web development after a long period of mainly working on large backend database apps, the suggestion of a nicely bundled a

Re: Full stack Clojure web/REST framework - is there any mileage in it?

You could just do: lein new fw1 myapp cd myapp lein run assuming you have nothing running on port 8080 already - otherwise: PORT=8123 lein run Noir also has a simple Leiningen template (although Noir is deprecated now): lein new noir noirapp cd noirapp lein run (same caveat applies regarding

Re: Full stack Clojure web/REST framework - is there any mileage in it?

Though the Clojure community has traditionally gone with smaller libraries rather than large frameworks, there is a full-stack web framework for Clojure called Conjure: https://github.com/macourtney/Conjure On Friday, January 11, 2013 11:52:05 AM UTC-5, Paul Umbers wrote: > > I've been experime

Re: Full stack Clojure web/REST framework - is there any mileage in it?

On Friday, 11 January 2013 12:17:35 UTC-7, Herwig Hochleitner wrote: > > > There is, however, value in curated sets of independent libriaries that > work well together. Also in having declarative syntax available for common > tasks. > Still IMO, Clojure's web story is still somewhat lacking on th

  1   2   >