3 ms·
You're right, it's probably in the eye of the beholder. To me something like a Clojure Ring app makes perfect sense. You get a request map, pipe it through a ba
by BadassFractal 13y ago
You're right, it's probably in the eye of the beholder. To me something like a Clojure Ring app makes perfect sense. You get a request map, pipe it through a bajillion functions until you hit the DB, then you take the results of your DB operations and pipe them back through a bajillion functions all the way back to HTTP.
- girvo 13y agoOh, request-response maps (heh) well to lisps; I copied Ring's API for my project. My biggest issue I guess, is getting out of a Class and Interface mindset. That said, do you have any advice for how to think about state in regards to web development? The database and its various assumptions were my biggest headache. What is the go-to library for Clojure here?
- islon 13y agoWell, in a typical web application (the server part) all your state is normally in the database so you don't need to worry about it. Just use pure functions that process the request get/put the data in the database and give the response. Do you have any specific needs for state other than the database?