What is the typical use-case for this or TorqueBox?
It started the JBoss process and at the end of it loaded my simple app. I tested it a little on the browser and ran the Apache benchmark tool on it like ab -n 1000 -c 10 http://127.0.0.1:8080/hello
After it had warmed up, further benchmark runs were much faster.
On my weak hardware, going up to 2.2k requests/second or something. I was like "wow! Give me more of that." Not really that it couldn't be matched by other technologies for that kind of stuff, but that it was a single process easily configured.
If we think that the same process could be shared by many other scripts, programs and so on, it's a good way to reuse all of that in innovative ways.
Deep down it's not much more than having a stable multi-threaded environment that you can rely on.
Then I thought: wait! When I started with Ruby, I was running from all of that kind of complexity!
It's as if we were being assimilated by Java again. Only this time we don't have to use so much Java or xml.
Disclaimer: I'm a TorqueBox/Immutant developer
Oh, and see here for what an applicaiton server is: http://en.wikipedia.org/wiki/Application_server
TorqueBox's home page explains the use-cases well.
The whole world isn't Silicon Valley; there are a lot of us out here who don't get to do the new-ooo!-shiny all the time.
Although I'm fully aware some firms are dysfunctional, it seems to require a strange alignment of the planets for someone to decide on using immutant.
11:01 < TimoT> aren't enterprise solutions like regular solutions but cost
11:01 < jsnell> they also don't work
Oh and there will be some certification program to train people in it.