Skip to content

links-lang/links

Folders and files

NameName
Last commit message
Last commit date

Latest commit

c7a899c · Oct 28, 2024
Jan 22, 2024
Mar 18, 2024
Oct 28, 2024
Nov 15, 2023
May 11, 2020
Oct 22, 2024
Nov 15, 2023
Mar 18, 2024
Sep 27, 2023
Nov 10, 2020
Oct 22, 2024
Oct 6, 2023
Jun 28, 2019
Feb 21, 2019
Jun 30, 2020
Jun 3, 2009
Jan 22, 2024
Jan 22, 2024
Jun 30, 2021
Nov 15, 2023
Jun 15, 2021
Sep 29, 2021
Jan 22, 2024
Feb 21, 2019
Dec 16, 2022
Nov 27, 2023
Nov 27, 2023
Nov 27, 2023
Mar 18, 2024
Nov 27, 2023
Oct 6, 2023
Nov 15, 2023
Jul 12, 2022
Oct 16, 2021

Repository files navigation

Links: Linking Theory to Practice for the Web

Build status

Links helps to build modern Ajax-style applications: those with significant client- and server-side components.

A typical, modern web program involves many "tiers": part of the program runs in the web browser, part runs on a web server, and part runs in specialized systems such as a relational database. To create such a program, the programmer must master a myriad of languages: the logic is written in a mixture of Java, Python, and Perl; the presentation in HTML; the GUI behavior in Javascript; and the queries are written in SQL or XQuery. There is no easy way to link these: to be sure, for example, that an HTML form or an SQL query produces the type of data that the Java code expects. This is called the impedance mismatch problem.

Links eases the impedance mismatch problem by providing a single language for all three tiers. The system is responsible for translating the code into suitable languages for each tier: for instance, translating some code into Javascript for the browser, some into Java for the server, and some into SQL to use the database.

Links incorporates ideas proven in other programming languages: database-query support from Kleisli, web-interaction proposals from PLT Scheme, and distributed-computing support from Erlang. On top of this, it adds some new web-centric features of its own.

FEATURES

  • Allows web programs to be written in a single programming language
  • Call-by-value functional language
  • Server / Client annotations
  • AJAX
  • Scalability through defunctionalised server continuations.
  • Statically typed database access a la Kleisli
  • Concurrent processes on the client and the server
  • Statically typed Erlang-esque message passing
  • Polymorphic records and variants
  • An effect system for supporting abstraction over database queries whilst guaranteeing that they can be efficiently compiled to SQL
  • Handlers for algebraic effects on the server-side and the client-side