@(#) $Id: Overview.html,v 1.34 1999/01/24 17:36:47 frystyk Exp $
Often extensions are deployed dynamically, extending existing applications. They motivate the need to independently introduce extensions and new features to HTTP in such a way that 1) They are orthogonal to other extensions. 2) They can be deployed automatically and dynamically.
This form for extensibility is not supported by HTTP/1.1 and PEP is a framework to satisfy these requirements.
The PEP specification has gone through a thorough design phase and entered a steady state where the authors do not intend to modify the document any further. At the same time we have developed practical experience with the PEP demo code which demonstrates both client, server, and proxy interactions using dynamic loaded PEP extensions. However, we believe that it is essential for a specification to be tested in real world applications before being deployed at large, which is the reason for the status of Experimental.
See the PEP change history for a list previous drafts of the PEP specification and the PEP Issues page with a list of open and closed issues on the draft.
There is now a small demo written in Java available that illustates some simple PEP scenarios. The demo can be downloaded and extended as it includes a complete PEP engine.