From: Michael Sullivan <mps@...>
Date: 2001-12-18T05:19:13+09:00
Subject: [ruby-talk:28818] Best way to do XML-RPC

Hi,

I'm trying to promote the use of Ruby on a project I'm working on.
Since I'm relatively new with the language, I'd like to hear what
others' thoughts are.  From what I've seen and done, I like the language
much better than Perl - can do more easier especially when dealing with
code in an Object Oriented way, too many OOP hoops to jump through to
force Perl to perform OO.

I was wondering what the various opinions of doing XML-RPC are.  I may
have non-Ruby applications connecting to my XML-RPC server such as Perl,
or Java.  So a couple of questions/thoughts:

Should I use a "stand-alone" server or CGI server?

Why?

CGI or mod_ruby?

What are the benefits and drawbacks of them?

Should I use SOAP4R?

On a related note, is there any way to have a persistent database
connection using mod_ruby?  Has anyone done this, or thought about how?
Global variables?  Shared memory?

Might a persistent database conenction be one reason why I might want to
use a stand-alone XML-RPC server?  The thought of using threads  for
multiple incoming connections RPC bothers me a bit, though - I know one
can do this single threaded, but I'm wondering about load and
scalability.

Thanks,

Mike

-- 
Michael P. Sullivan                                  
Distributed Computing Systems, LLC                         Cell: 516-429-2080 
E-Mail: mps@discomsys.com                           http://www.discomsys.com/ 
    * UNIX Systems and Database Consulting, Architecture and Management *
"Failing to plan, is planning to fail... plan for the worst, hope for the best"