Thank you guys for your help! To Xavier's words: So if i am understanding you correctly, Mongrel is capable of transforming HTTP requests to invocations of the Rails dispatcher, and, on the other side, transforming the result from the Rails application back to a HTTP response. So it seems that Mongrel is just a web server, that is a mediator to the Rails application, just like the good old CGI ideology ? Which is also present in the JavaEE case, but with the significant difference that, apart from transforming the HTTP request to a servlet invocation, the web container is THE execution environment, and it handles the complete life cycle of the servlet/JSPs...... In this sense, i see that Mongrel does not handle the life cycle of the Rails component, does it ?
And fianlly, i would also like to ask you some more questions. Consider a typical Rails application, running inside Mongrel. What possibilities do there exist for my Ruby code (of the Rails application) to call/execute Java code ? What is the relation between Mongrel and Java ? From the home page of Mongrel, after i downloaded the Mongrel archive, it seems that it is an application, written in pure Ruby (except for the HTTP parser, which could be written in C or Java). What is the Mongrel <-> Java integration ? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
