Date   : Thu, 30 Jul 2009 08:08:13 +0100
From   : info@... (Sprow)
Subject: RFC: BBC Ethernet API

Hi,
Thinking a bit more about this, as well as a BSD sockets interface,
presumably access to the DNS resolver would be useful?

Admittedly, if you have the socket interface you could write your own
resolver by opening the appropriate port, but that seems like a bit of a
waste of effort if there's already one I use.

Wholeheartedly ripping off the RISC OS API again we would have
  DNSResolver_GetHostByName
  DNSResolver_GetHostByAddr
and maybe the more complex multitasking version
  DNSResolver_Start
  DNSResolver_Check
  DNSResolver_GetAnswer
  DNSResolver_Dispose

Isn't there an OSWord set aside for RISC OS SWI emulation already?
Would it be simpler to directly translate the Socket and DNSResolver SWIs
into a single OSWord?

While I have the manual open, other SWI families are
  DNSResolver - as discussed
  Ec          - no plans to implement
  ESocket     - no plans to implement
  Freeway     - no plans to implement
  HTMLDecode  - see WebBC
  HTTP        - see WebBC
  Internet    - no plans to implement
  Mbuf        - internal use
  MimeMap     - no plans to implement
  PPPdriver   - not needed
  Resolver    - as discussed
  ShareFS     - no plans to implement
  SLIPdriver  - not needed
  Socket      - see JGH's earlier message
  SysLog      - no plans to implement
  URI         - see WebBC
  WebFTP      - for use with browsers
  WebGopher   - for use with browsers

so I think Sockets and DNSResolver are the only useful bits in this
situation, right?
Sprow.