Since deployed GAE apps use something that works like Jetty you could just develop against Compojure and make sure you aren't doing anything that launches a new thread. Then do sanity checks against the dev server before deploying. This way you get the speed of REPL style development, and only get slowed down when you're ready to really test your stuff against GAE. David
On Wed, May 13, 2009 at 5:35 PM, Kees-Jochem Wehrmeijer <henc...@gmail.com>wrote: > > Hi everybody, > > I started playing with Clojure on Google App Engine. By following the > experiences of others (http://elhumidor.blogspot.com/2009/04/clojure- > on-google-appengine.html and > http://www.fatvat.co.uk/2009/05/clojure-on-google-app-engine.html > mostly) I was able to get something running quite quickly. However, > something that annoys me is that I have to recompile every time I make > a change. I'm still learning Clojure (and Emacs) but I'd already > gotten quite used to using the REPL. So I was wondering if anybody > else already had some experience with using Clojure on GAE and what > your workflow looks like. > > cheers, > Kees > > > --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
