Many web applications deal in complex transactions, and employ a workflow process for the construction of a transaction. Many others construct an application object or object set through a more general process of interactive updating or construction. Both are constructive.

The "static files service" is the first class of REST applications [1][2]. The delivery of static content files over HTTP has the fastest response time and the lowest response latency.

Dynamic interaction with server side applications (for example database or chat) invokes application programming. A class of dynamic programming is defined in RESP as an extension to REST. We want to identify dynamic services with good response and low latency for internet scale.

RESP posits that an editing protocol permits arbitrarily complex constructrions on the server side through its operators. These operations need to evaluate in linear or sublinear time for scalability. Operations that are good for a graphical user interface are also good for mashups -- using AJAX, Flash or Java.

The purpose of any style is to identify something generally useful.

The initial RESP paper (October 9 & 11, 2006) interlaced some machine theory to work on the classification and definition of network interfaces as network automatons.

Monday November 26, 2007