Re: Ruby on Rails?

Mont,

>  Just to be clear, I wasn't looking for EOF in Rails, it was just a 
> point of reference.

Perfectly understandable. I think if you have worked with EOF before, 
you will naturally approach Rails from this perspective.

>  It sound like Rails is *primarily* targeted at stateless 
> applications.  Those that do not maintain application state in memory 
> between separate request/response transactions.  I am not saying that 
> it can't be used for state-full applications, just that stateless is 
> the most common type of application, and therefore the direction that 
> the various support tools and frameworks help most with.

Not quite. As in WO, there's a session object that stores application 
state for each user. A web application that does not maintain state at 
all would be quite pointless. There are restrictions on what kind of 
objects you can store in a session (i.e. they must be serializable). 
But the overall concept is the same as in WOF and other frameworks.

RoR does not have stateful components like WO. Every component (or 
controller in Rails parlance) is stateless. It pulls state information 
from the session or it gets passed in when the controller is invoked 
(usually from a routed request).

Cheers,
Andreas