From: "Bjørn Nordbø" <bn@...>
Date: 2002-08-06T17:00:41+09:00
Subject: Re: Ruby/Perl: tight integration

<bbense+comp.lang.ruby.Aug.05.02@telemark.stanford.edu> 
> In article <Ttv39.1735$0p1.20014@news2.ulv.nextra.no>,
> Bj�rn Nordb�  <bn@strangedays.no> wrote:
>>Other alternatives seems to be SOAP og XML-RPC; however I am a little
>>concerned about the performance of XML based solutions; the supervise
>>process needs to scale to about 80 operations/second, with bursts of
>>twice that.
> 
> - - Hmm, that's pretty hefty for any scripted server to deal with
> on a single processor. It certainly can be done, but you might
> have to write your own protocol to get this performance.

Actually, I do have an option of writing a multithreaded server and
distributing the load over several CPUs. However this would defeat
my idea of using XML-RPC or similiar to simplify the server.

>>Does anyone have practical experience with the performance of SOAP og
>>XML-RPC for Ruby? Or know of viable alternatives?
> 
> - - If you're designing your own protocol for this you might want
>   to look at BEEP. It's still XML, but has less overhead than 
>   either SOAP or XML-RPC. Unfortunately, the ruby implementation
>   seems to be mostly vaporware at this point. 

BEEP is a new one, but without a Ruby implementation it's pretty much
useless. I don't have the time or knowledge to implement a protocol
library yet; this is my first large Ruby project.

Thanks for your answers!

-- 
I've seen things you people wouldn't believe. Attack ships on fire off
the shores of the Nonestic Ocean. I watched magic blunderbusses flash
and glitter in the dark near Glindea's Palace. All those moments will
be lost in time, like tears in rain. Time to die...