From: bbense+comp.lang.ruby.Aug.05.02@... Date: 2002-08-06T02:39:19+09:00 Subject: Re: Ruby/Perl: tight integration -----BEGIN PGP SIGNED MESSAGE----- In article , Bj�rn Nordb� wrote: >Hello, > >I'm planning to write a system consisting of a supervise process (which >I want to write in Ruby) and several transaction processes (written in >Perl due to library issues). I have spent some time now, looking at Rinn, >but it doesn't support long long and all in all, it doesn't seem like >something you'd use for a production system yet. > >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. > >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. - - Booker C. Bense -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBPU6zpgD83u1ILnWNAQGfEwP+O/jQSuGEwwMQiffUcVmO18w40kge18GA i0Vs4pJJTHCZAbnU7V/wrj5KStDwTyntgEuRq8t1Ckjr+ER1xsmfFj9W0acbqcxA PCoLieUNP6FITEFfcuryv+u2qhyIuK6sVoxcJ6Efiwwfjif8ybUu2Mgdvr62NTzf 73+mRU8IN2s= =mWbZ -----END PGP SIGNATURE----- --