HTML and CSS Reference
Data for the first part
Data for the second part
The preceding example has two document parts, both composed of just
plain text. The server sends each part, preceded by our SomeRandomString
document-boundary delimiter (which itself is preceded by two dashes),
followed by the Content-Type field and then the data for each part. The
last transmission from server to client is a single reference to the bound-
ary string, followed by two more dashes indicating that this was the last
part of the document.
Upon receipt of each part, the Mozilla browser automatically adds the
incoming data to the current document display.
You have to write a special HTTP server application to enable this type of
server-push dynamic documentone that creates the special HTTP MIME
multipart/mixed header and sends the various documents separated by
the boundary delimiter.
13.3.2. The Multipart/X-Mixed-Replace Media Type
Server-push dynamic document authors may use an experimental vari-
ant of the MIME multipart/mixed media type known as multipart/x-
mixed-replace media . The difference between this special content type
and its predecessor is that, instead of simply adding content to the cur-
rent display, the "replace" version has each subsequent part replace the