Howdy Bo:
 
> I believe IRC uses UDP which should be fully supported very soon.
 
Actually, IRC uses TCP/IP, as indicated in the rfc:

  http://www.irchelp.org/irchelp/rfc/

  This rfc lays out what we need to do to implement IRC in
  REBOL. Which reminds me...  if people are interested in building
  this protocol as well as things like xml-rpc, you'll probably get it
  done quicker than we will at REBOL Tech.  We're rather swamped with
  some larger projects right now, but I would be eager to lend some
  amount of dedicated technical assistance to people trying to
  implement these protocols.

  It seems like IRC would be handled with a persistent port and
  working something like nntp.r, ie:

    irc-port: open irc://somehost.com
    insert irc-port [nick "whoever"]
    insert irc-port [join "#rebol"]

  etc..  ie, wrap IRC's primitive operations. The protocol is too
  complex to be handled by simple one liners.  In fact, with some
  effort nntp.r itself could be hacked into doing IRC.

  Now, xml-rpc seems like it could be done in a more direct way, ie:

  write xml-rpc://somesite [func-name [param1 param2 param3 . . .]]

  Results would be returned to REBOL format, so in essence the xml is
  never seen, just used as the marshaling behind the scenes.

  Well, those are my thoughts..  if interested in working on something
  like this, send me mail directly ([EMAIL PROTECTED]) and I'll do what I
  can to coordinate efforts and assist on the technical side of the
  port handlers. I'll bet other REBOL Tech. crew will help out too
  where possible.  I'm just forwarding this idea on my own
  initiative-- that's all.  United and strong--

  Saludos--

  -jeff

Reply via email to