I'm curious if anyone's given any thought to this. I think we should consider blurring the lines between client and server at a source-level.
Half-baked ideas: Compiler enforced 'ABI' for server calls. Tooling to jump across couplings, ie treating the XHR->Compojure boundary like a simple function call. Perhaps frameworks can 'register' their schemes at dev-time. URL-tree navigation, docs via something like the Prismatic Schema Swagger integration. Reusable ring-handlers to go along with reusable components. With access to the CLJS analyzer as demonstrated by cider-nrepl, I think it's possible to make these connections when combined with a CLJ server repl, either shared in the same process, or decoupled, doesn't matter :-). Too many possibilities! -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
