-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Andrew Jackson edited this page Nov 27, 2013
·
9 revisions
The idea is to augment existing web-based access system in order to provide our communities with alternative forms of access for 'difficult' content types.
There are two components in this architecture:
- The Response Sniffer: This monitors requests and responses on and sniffs out the content types involved. For types that are known to be problematic, the user is redirected to the second component.
- The Interjection Service: This takes a URL as an argument, and provides alternative representations of the original resource. It can be called directly, or during playback via the Response Sniffer.
The diagram below illustrates how the two components work together.
This repository contains prototype implementations of these two components:
The interject-servlet-filter performs the role of a Response Sniffer. It can be deployed over any Java Servlet application, and the initial target will be OpenWayback.
The interject-webapp provides the Interjection Service. It contains some example transformation services.
