From: Ray Capozzi <Ray_Capozzi@...>
Date: 2003-03-10T11:43:16+09:00
Subject: Re: Protocols

Thanks for the suggestion.  It looks promising.  I'd like to be able to
telnet to the servers port without the need of speaking yaml to the sever
from the telnet session.  It seems that I'd have to adopt yaml whole-hog on
the Ruby side.  From the docs, the Yaml methods closes the IO channel upon
doc read.  I can see two approaches.  First, include a tag at the start of a
session to determine a protocol.  Alternatively, I could create a specific
control port process just for telnet.  Perhaps there is another alternative.
I could modify the Yaml stuff to not close the channel after reading a doc.

Thanks again for the clue-in.



"MikkelFJ" <mikkelfj-anti-spam@bigfoot.com> wrote in message
news:3e6be668$0$136$edfadb0f@dtext01.news.tele.dk...
>
> "Ray Capozzi" <Ray_Capozzi@hotmail.com> wrote in message
> news:5lRaa.179166$4F3.11146475@news2.east.cox.net...
>
> > Is there a preferred set of ruby libraries for client/server solutions?
> As
> > an example, RPC.  The protocol needs to exist for Ruby and Perl, so
druby
> > wont work.  XML-RPC seems to be the leading candidate, despite my
> objectives
> > to XML.
>
> Try search the archives for YAML over the past week or two. There is work
in
> progess using a YAML transport layer on place of Ruby marshalling.
>
> Mikkel
>
>