Re: [jruby-user] Business-logic tier - "enterprise" integration

On Nov 19, 2007 5:31 AM, Stefan Magnus Landrø <stefan.landro@xxxxxxxxx> wrote:
> For security reasons, my client wants the business-logic in our rails-app to 
> be separated from the view-layer

Doing this for security reasons is way overrated, if not outright
wrong, but nobody seems to know how to evaluate security measures
objectively (I certainly don't), so this is just a humble opinion.
Although it is shared by so many other people in ThoughtWorks, it's
one of the nearest approxiomations to "The Official Point Of View" on
a technology subject this company has. Our advice on this issue is
often ignored because Security Is More Important, so it's also a bit
of a sensitive spot :)

>From application's point of view, this is an obviously inconvenient
constraint, because inefficiencies of moviong stuff across the wire
will inevitably force much more coarse-grained interaction between
view and model than is otherwise desirable, and more than Rails
actually was designed for. You will most likely have to introduce a
service layer between controller and model, and kiss goodbye to most
acts_as_X plugins.

That was the sad part. Now, on to constructive advice.

> What should we opt for?
ARes where it makes sense, plain HTTP GET or POST where it doesn't
(e.g., for methods that return string or boolean, or where a
coarse-grained service otherwise doesn't fit the resource paradigm).

Definitely avoid SOAP, even though it should be much less painful with
existing Java WS-* stacks than it is with MRI. For two tightly coupled
parts of the same app to talk to each other, you don't need any of the
WS-* features. The extra strain all those angled brackets place on
both production servers and developers' brains is huge though.

-- 
Alexey Verkhovsky
CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com]
RubyWorks [http://rubyworks.thoughtworks.com]

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email