Re: Ruby on Rails?

Again, thanks. That gives me a much better picture of Rails.

I have been doing data-centric/transactional applications for so long that I
sometimes have trouble conceptualizing other types of apps.

It would seem that Rails and WO are best suited to different types of
applications. I am sure they can both be made to work for all web
applications, but they each have their strengths. Rails in approachability
and WOs in more complex architectures.

The trouble seems to be knowing when to use which tool, and what to do when
an app that was best served by one too morphs into one that would be better
suited by the other.

I guess I wish for a tool that lets you start an app as quickly and easily
as I hear Rails does, but lets you grow into the type of more complex
architecture supported by WO.

Perhaps Rails will get there some day.

-Mont


On 10/28/05, Andreas Korth <[email protected]> wrote:
>
> 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
>