Drb / ActiveRecord as Application Server for Qt/Ruby client

ruby-talk
1

Hi,

I intend to start a new project with the following architecture:

Server:

···

-------
- Postgresql database
- ActiveRecord
- Distributed Ruby Server

Client:
-------
- Distributed Ruby Client
- Qt/Ruby GUI

Drb is not really an "Application Server". Normally, you expect features like "Connection Pooling" from such a server, and much more.

Is it safe and robust, anyway, on an intranet composed of a hundred of client computers, to marshall all ActiveRecord objects through a simple drb server?

Has anyone done this already?

Your reactions are more than welcome!

Thanks

----------------------------------
Philippe Lang, Ing. Dipl. EPFL
Attik System

2

Hi,

I intend to start a new project with the following architecture:

Server:
-------
- Postgresql database
- ActiveRecord
- Distributed Ruby Server

Client:
-------
- Distributed Ruby Client
- Qt/Ruby GUI

Drb is not really an "Application Server". Normally, you expect features like "Connection Pooling" from such a server, and much more.

Is it safe and robust, anyway, on an intranet composed of a hundred of client computers, to marshall all ActiveRecord objects through a simple drb server?

Has anyone done this already?

Your reactions are more than welcome!

Thanks

If you are just gonna marshal the AR objects and send them across the network, why even have a server / client architecture? Just stick the AR code in the "Client" and let PostgreSQL worry about concurrency.

···

On Aug 4, 2006, at 3:24 AM, Philippe Lang wrote:

----------------------------------
Philippe Lang, Ing. Dipl. EPFL
Attik System