./www/libecap, C++ implementation of eCAP API

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 1.0.1nb2, Package name: libecap-1.0.1nb2, Maintainer: prlw1

eCAP is a software interface that allows a network application,
such as an HTTP proxy or an ICAP server, to outsource content
analysis and adaptation to a loadable module. For each applicable
protocol message being processed, an eCAP-enabled host application
supplies the message details to the adaptation module and gets back
an adapted message, a "not interested" response, or a "block this
message now!" instruction. These exchanges often include message
bodies.

The adaptation module can also exchange meta-information with the
host application to supply additional details such as configuration
options, a reason behind the decision to ignore a message, or a
detected virus name.

If you are familiar with the ICAP protocol (RFC 3507), then you
may think of eCAP as an "embedded ICAP", where network interactions
with an ICAP server are replaced with function calls to an adaptation
module.

The libecap library implements the eCAP API in C++.


Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 89533c2ac77fee7b26f53c20c25a1423ce1498b7
RMD160: 72cac0074be057805511d33156baacb0eeaef4ed
Filesize: 331.835 KB

Version history: (Expand)


CVS history: (Expand)


   2017-05-03 10:38:46 by Jonathan Perkin | Files touched by this commit (95)
Log message:
Convert CXXFLAGS setting C++ standard to USE_LANGUAGES.
   2016-06-23 17:05:38 by Patrick Welche | Files touched by this commit (3)
Log message:
Fix previous by going the whole hog and requiring C++11.
   2016-06-21 19:57:07 by Joerg Sonnenberger | Files touched by this commit (1)
Log message:
Don't use the obsolete TR1 interface for C++11 or libc++. Bump revision.
   2016-06-17 18:39:55 by Patrick Welche | Files touched by this commit (5)
Log message:
Add libecap 1.0.1

eCAP is a software interface that allows a network application,
such as an HTTP proxy or an ICAP server, to outsource content
analysis and adaptation to a loadable module. For each applicable
protocol message being processed, an eCAP-enabled host application
supplies the message details to the adaptation module and gets back
an adapted message, a "not interested" response, or a "block this
message now!" instruction.  These exchanges often include message
bodies.

The adaptation module can also exchange meta-information with the
host application to supply additional details such as configuration
options, a reason behind the decision to ignore a message, or a
detected virus name.

If you are familiar with the ICAP protocol (RFC 3507), then you
may think of eCAP as an "embedded ICAP", where network interactions
with an ICAP server are replaced with function calls to an adaptation
module.

The libecap library implements the eCAP API in C++.