This directory contains generic implementations of the Content interface. A content objects is
used to represent the "content" of a transaction, usually streaming data (HTML
page, JPEG file, etc.) being sent from a Web server to a browser. The
content interface provides a very generic way for agents to get access to or modify the data in
transit. Some agents (e.g. cache agent) grab a copy of the data and put
it into a file (using the tapIn or tapOut methods), while
others modify the data (e.g. Proxie inserts a toolbar just after the body
tag of HTML pages using the add method).
The content classes in this directory are normally instantiated by a ContentFactory. The default ContentFactory uses mime type to find a name of the corresponding content class, so text/html.class would be the class instantiated for data of type text/html. If no specific type is found a default is used ByteStreamContent.
All of these classes inherit from StreamingContent which provides all of the
machinery for a circular buffer. It also keeps track of state changes and
uses that to notify interested agents when at appropriate times.
In theory, new content classes can be implemented by subclassing
StreamingContent and providing appropriate readData and
writeData methods.
Note that
these classes are complicated by the fact that we want to start shipping the
data out to a browser as soon as possible (without waiting for the entire data
structure to be in memory), so a content object has to keep track of any
modifications specified by an agent and perform them at the appropriate time
as the data is being shipped through the circular buffer.
Name Last modified Size Description
Parent Directory - ByteStreamContent.java 2012-04-01 16:18 2.7K GenericContent.java 2012-04-01 16:18 10K Makefile 2012-04-01 16:18 1.3K StreamingContent.java 2012-04-01 16:18 16K text/ 2012-04-01 16:18 -