---- Trying to use CGI sounds like a bad idea. It's always full of ---- security issues
I have read trough the page that you linked to and the issues listed ain't any different from the issues associated with developing PHP applications. ---- I mostly agree with the above, just to extend it a bit: PHP is an ---- interpreter which means a new process is fired up on every request. ---- Java is abysmally slow if you try to use it in the same way since you ---- have to instantiate the whole VM everytime (besides the fact that you ---- have to serialize all state incl. caches to disk to survive a ---- request). Why is the jvm so slow at starting up? Both PHP and Python are byte code compiled and run in a VM, but the runtime environments for both of these languages start up almost instantly. ---- Rant: I also find it annoying and unnecessarily complex to have JVM ---- based webapplications running online. Not many managed JVM ---- environments are available in comparison to PHP, Python, Perl, Ruby, ---- et al. The reason is that until now it's still not really possible to ---- reliably partition applications (code, resources consumption, kill of ---- only one applicaton) within a single JVM, that means, JVM don't really ---- mix with shared hosting plans (the solutions are so called MVMs with ---- true separation of resources inside a JVM). Until these MVMs arrive, ---- you really need are Hypervisor based solutions, Xen etc. to constrain ---- ressource usage. I hope that someone is going to tackle that problem ---- soon, there's a pile of cash waiting to be made if you can pull it off ---- for the masses. This is exactly why I do not want the complexity of proxying various servers behind apache, I am running my own development server, which is set up to mimic the average shared hosting environment, PHP and CGI applications run as separate users to prevent the compromise of one application form effecting anything else. Running other servers doesn't fit with this environment very well, and embedding more modules into apache is something that I am trying to avoid, as they often provide no way of running code as different users. ---- You could use FastCGI to accomplish this, though you would have to ---- write the interface. ---- http://www.fastcgi.com/ ---- FastCGI would remove the long startup times for the JVM, etc. I will look into fast CGI. ---- One thing I would say, though, is that PHP apps don't "Just Work", you ---- have to have mod_php (in Apache) or ---- some other support in the web server. I know, however from the viewpoint of the end user, php does just work, just upload a .php file, and run it. Which is why PHP has bean so successful compared to other technologies, even though the language is a complete mess. ---- If you want very easy to deploy web apps, I would suggest Compojure: ---- http://github.com/weavejester/compojure/tree/master ---- You can always use a proxy to front a compojure app, which is how a ---- lot of web apps do it. Compojure requires running a second server and proxying it, which as described above, I am trying to avoid. Is there any way of developing a application with Compojure completely without shell access to the server? Lisp seams like a very good language for developing web applications, mostly due to its macro system and doorman specific languages. However there seam to be no practical ways of developing with it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
