Concepts in Programming Languages – University of Cambridge Course

The following are all copy and pasted from a University of Cambridge course link to the website below. It was accessible by public, so I figured I should dump it here. Maybe I can read some of this when I have a vacation.

Lecture slides

  • Introduction and motivation.
    Additional reading material:
  • K. ZusePlankalkul.
  • The first procedural language: FORTRAN (1954-58).
    Additional reading material:
  • Fortran.
  • The first declarative language: LISP (1958-62).
    Additional reading material:
  • J. McCarthyRecursive functions of symbolic expressions and their computation by machine.
    Communications of the ACM, 3(4):184-195, 1960.
  • Block-structured procedural languages: Algol (1958-68) and Pascal (1970).
    AppendixBCPL (1967) and C (1971-78)
    Additional reading material:
  • D. E. KnuthThe remaining trouble spots in ALGOL 60.
    Communications of the ACM, Volume 10, Issue 10, pages 611-618, 1967.
  • B. KerninghanWhy Pascal is not my favorite programming language.
    AT&T Bell Laboratories. Computing Science Technical Report No. 100, 1981.
  • Object-oriented languages — Concepts and origins: SIMULA (1964-67) and Smalltalk (1971-80).
    SML codeObjects in SML!?
    Programming languageSqueak.
    Additional reading material:
  • A. C. KayThe early history of Smalltalk.
    ACM SIGPLAN Notices, Volume 28, No. 3, 1993.
  • P. WegnerConcepts and Paradigms of Object-Oriented Programming
    Expansion of OOPSLA-89 Keynote Talk.
  • B. StroustrupWhat is Object-Oriented Programming? (1991 revised version).
    Proc. 1st European Software Festival. February, 1991.
  • Types in programming languages: ML (1973-1978).
    Additional reading material:
  • A. Koenig. An anecdote about ML type inference.
    USENIX Symp. on Very High Level Languages, 1994.
  • Data abstraction and modularity: SML Modules (1984-97).
    Additional reading material:
  • M. TofteFour Lectures on Standard ML.
    LFCS Report Series ECS-LFCS-89-73, 1989.
  • The state of the art: Scala (2004-2006).
    Programming languageScala.
    Additional reading material:
  • M. Odersky et alAn overview of the Scala programming language.
    Technical Report LAMP-REPORT-2006-001, Second Edition, 2006.
  • M. Odersky et alA Tour of the Scala Programming Language.
    Programming Methods Laboratory, EPFL, 2007.
  • M. OderskyScala By Example.
    Programming Methods Laboratory, EPFL, 2008.
  • Books

  • Main:
  • M. ScottProgramming Language Pragmatics (2nd edition).
    Morgan Kaufmann, 2006.
  • J.C. MitchellConcepts in programming languages.
    Cambridge University Press, 2003.
  • T.W.Pratt and M.V.ZelkowitzProgramming Languages: Design and implementation (3rd edition).
    Prentice Hall, 1999.
  • Other:
  • R. L. Wexelblat (ed.). History of Programming Languages.
    ACM Monograph Series, 1981.
  • N. Metropolis, J. Howlett, G.-C. Rota (eds.). A History of Computing in the Twentieth Century: A Colletion of Essays.
    Academic Press, 1980.
  • T.J. Bergin and R. G. Gibson (eds.). History of programming languages – II.
    ACM Press, 1996.
  • [Actual Course Website]

    Lightweight Directory Access Protocol

    I need to learn to use LDAP for an upcoming project, so I will start to keep some notes here. A lot of this post will be copy and pasted and Wikipedia and other sources.

    A client starts LDAP session by connection to an LDAP server, called a Directory System Agent (DSA).
    The default port is TCP port 389. The client sends an operation request to server and server responds. Client can start sending more requests before responses, however the server may send responses in any oreder.

    Protocal Overview: 

    • StartTLS — use the LDAPv3 Transport Layer Security (TLS) extension for a secure connection
    • Bind — authenticate and specify LDAP protocol version
    • Search — search for and/or retrieve directory entries
    • Compare — test if a named entry contains a given attribute value
    • Add a new entry
    • Delete an entry
    • Modify an entry
    • Modify Distinguished Name (DN) — move or rename an entry
    • Abandon — abort a previous request
    • Extended Operation — generic operation used to define other operations
    • Unbind — close the connection (not the inverse of Bind)

    Directory Structure

    • A entry in the Directory can contain a set of attributes
    • An attribute has a name and possibly multiple values — the attributes are defined in a schema 
    • Each entry has a unique identifier: its Distinguished Name (DN). This consists of its Relative Distinguished Name (RDN), constructed from some attribute(s) in the entry, followed by the parent entry’s DN. Think of the DN as the full file path and the RDN as its relative filename in its parent folder (e.g. if /foo/bar/myfile.txt were the DN, then myfile.txt would be the RDN).

    Operations

    The option I am most interested in currently is

    Bind (authenticate)

    The Bind operation establishes the authentication state for a connection.

    Simple Bind can send the user’s DN and password in plaintext, so the connection should be protected usingTransport Layer Security (TLS). The server typically checks the password against the userPassword attribute in the named entry.

    Anonymous Bind (with empty DN and password) resets the connection to anonymous state.

    SASL (Simple Authentication and Security Layer) Bind provides authentication services through a wide range of mechanisms, e.g. Kerberos or the client certificate sent with TLS.

    Bind also sets the LDAP protocol version. The version is an integer and at present must be either 2 (two) or 3 (three), although the standard supports integers between 1 and 127 (inclusive) in the protocol. If the client requests a version that the server does not support, the server must set the result code in the bind response to the code for a protocol error. Normally clients should use LDAPv3, which is the default in the protocol but not always in LDAP libraries.

    Bind had to be the first operation in a session in LDAPv2, but is not required in LDAPv3 (the current LDAP version).

    [wiki link]

    Other links for my reading on this:

    OpenLDAP

    LDAP tutorial

    PHP LDAP FUNCTIONS