This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-05
Channels
- # beginners (29)
- # boot (29)
- # cider (54)
- # cljs-dev (99)
- # cljsjs (31)
- # cljsrn (39)
- # clojars (32)
- # clojure (171)
- # clojure-austin (2)
- # clojure-berlin (5)
- # clojure-brasil (3)
- # clojure-greece (2)
- # clojure-italy (1)
- # clojure-korea (11)
- # clojure-spec (202)
- # clojure-uk (166)
- # clojurescript (130)
- # cursive (54)
- # datomic (99)
- # dirac (18)
- # figwheel (6)
- # hoplon (23)
- # lambdaisland (3)
- # leiningen (8)
- # luminus (14)
- # off-topic (11)
- # om (3)
- # om-next (24)
- # onyx (59)
- # planck (25)
- # protorepl (10)
- # re-frame (49)
- # reagent (14)
- # ring-swagger (2)
- # rum (46)
- # schema (1)
- # slack-help (6)
- # specter (7)
- # testing (7)
- # untangled (115)
- # yada (1)
@tankthinks: (let's move here as it's a bit off main clojure)
good call
@tankthinks: I tend to go off topic. 🙂 couchdb is an erlang database that's eventually consistent right?
@tankthinks: what I want -- if Google App Engine did NOT have a 30-second limitation and allowed for websockets -- that'd be pretty close to my ideal setup; lacking that, I need a webserver of my own to support websockets ;;
following http://lambda-startup.com/developing-clojure-on-app-engine/ I even managed to get clojure to run on GAE under the "java platform"
if you need websockets, couchdb is probably not for you
the main things GAE is not provding for me at the moment is real time communication -- like real time chat and shared 'whiteboard' (done in svg)
i see … yes … couchdb has some neat properties … and when you said you basically needed an API (with Auth) in front of a DB … that is couchdb