# Re: Drb / ActiveRecord as Application Server for Qt/Ruby cli

**URL:** <https://www.ruby-forum.com/t/re-drb-activerecord-as-application-server-for-qt-ruby-cli/101574>\
**Category:** Ruby\
**Created:** [August 6, 2006, 10:58am UTC](https://www.ruby-forum.com/t/re-drb-activerecord-as-application-server-for-qt-ruby-cli/101574 "2006-08-06T10:58:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![philpraxis](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/77aa72/32.png) [@philpraxis](https://www.ruby-forum.com/u/philpraxis)\
**Post date:** [August 6, 2006, 10:58am UTC](https://www.ruby-forum.com/t/re-drb-activerecord-as-application-server-for-qt-ruby-cli/101574/1 "2006-08-06T10:58:34Z")

</div>

Adam K. wrote:

> On Aug 4, 2006, at 12:20 PM, Philippe L. wrote:
> 
> > I prefer a 3-tier approach, with all the buisness logic on the  
> > server, just like you would do with J2EE. Centralisation of code is  
> > a good thing I think.
> 
> You’re already using ActiveRecord…why not throw the rest of  
> the Rails stack in and use REST, XML-RPC or SOAP?

Hi,

Transfering ActiveRecord objects to the client through Drb,  
transparently, appears to me to be much more effective than using an  
API, like the one you get with a REST-enabled server. But REST could be  
an option, yes. I have just asked the Qt team if the link between REST  
and Qt is easy to do.