Whither Sockets?

The article discusses sockets API (application programming interface). The author examines the conditions present when sockets API was developed in 1982 at the University of California Berkeley, as well as exploring the manner in which such conditions informed the way networking code has been writte...

Descripción completa

Detalles Bibliográficos
Publicado en:Communications of the ACM Vol. 52; no. 6; pp. 51 - 56
Autor principal: NEVILLE-NEIL, GEORGE V.
Formato: Artículo
Publicado: Association for Computing Machinery Jun2009
Materias:
Acceso en línea:Ver este registro en EBSCOhost
fields @attributes:
  recordID: 1
pdfLink:
plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=40217613&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 40217613
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00010782
        ACM
      jtl: Communications of the ACM
      issn: 00010782
      maglogo: N
    pubinfo:
      dt: Jun2009
      vid: 52
      iid: 6
      pid: 68
      pub: Association for Computing Machinery
    artinfo:
      ui:
        40217613
        10.1145/1516046.1516061
      ppf: 51
      ppct: 5
      formats:
      tig:
        atl: Whither Sockets?
      aug:
        au: NEVILLE-NEIL, GEORGE V.
      su:
        Application program interfaces
        Computer operating systems
        Computer networks
        Information technology
        Application software
        University of California, Berkeley
      sug:
        subj:
          Application program interfaces
          Computer operating systems
          Computer networks
          Information technology
          Application software
          University of California, Berkeley
      ab: The article discusses sockets API (application programming interface). The author examines the conditions present when sockets API was developed in 1982 at the University of California Berkeley, as well as exploring the manner in which such conditions informed the way networking code has been written. Additionally, the author describes developers' attempts to work around inherent limitations built into sockets API. Other topics include the future of sockets given the changes occurring in computer networks.
      pubtype: Periodical
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2009
    holdings:
      @attributes:
        islocal: N