HTTP/1.1 200 OK Date: Tue, 24 Nov 2009 03:47:33 GMT Server: Apache/2.2.6 (Fedora) Last-Modified: Tue, 11 Apr 1995 07:04:38 GMT ETag: "73cbd-6d4-f7ba0d80" Accept-Ranges: bytes Content-Length: 1748 Connection: close Content-Type: text/html; charset=UTF-8

Client extensibility

Reasons PRO

Provide fine-grained interactivity at the client (such as validation of coupled input fields, or custom event handling for graphical input).
Balance computation, not just state, between client/server (server reources and data may not be required for all computations).
Provide a stateless substitute for server-to-client callbacks (through client-to-server callbacks initiated by smart extensions).

Reasons CON

Hard to get the right mixture of flexibility vs. security for a client-side extension mechanism.

Subsidiary Design Requirements

Format- and language-independent client extension framework ("object model").
Interpreted extensions ("scripting").
Byte-compiled extensions ("virtual machines").
Binary extensions ("components").

Updated: Tue Apr 11 1995
Up to Interactive Standards Home Page.

HyperNews Responses

1. Untitled () 1. kelwyn ()