plone

libe-book-doc-0.1.3-19.fc36.noarch
The libe-book-doc package contains documentation files for libe-book.
Located in LBN / … / Core Linux / BastionLinux 36
libe-book-tools-0.1.3-19.fc36.x86_64
Tools to transform e-books into other formats. Currently supported: XHTML, raw, text.
Located in LBN / … / Core Linux / BastionLinux 36
libebml-1.2.2-2.lbn13.x86_64
Extensible Binary Meta Language access library A library for reading and writing files with the Extensible Binary Meta Language, a binary pendant to XML.
Located in LBN / … / Core Linux / BastionLinux 13
libebml-1.2.2-3.fc18.armv6hl
Extensible Binary Meta Language access library A library for reading and writing files with the Extensible Binary Meta Language, a binary pendant to XML.
Located in LBN / … / Core Linux / BastionLinux 13
libebml-1.3.0-1.fc19.armv6hl
Extensible Binary Meta Language access library A library for reading and writing files with the Extensible Binary Meta Language, a binary pendant to XML.
Located in LBN / … / Core Linux / BastionLinux 19
libebml-1.3.3-1.lbn19.x86_64
Extensible Binary Meta Language access library A library for reading and writing files with the Extensible Binary Meta Language, a binary pendant to XML.
Located in LBN / … / Core Linux / BastionLinux 19
libebml-1.3.6-3.lbn25.x86_64
Extensible Binary Meta Language access library A library for reading and writing files with the Extensible Binary Meta Language, a binary pendant to XML.
Located in LBN / … / Core Linux / BastionLinux 25
libecap-0.2.0-3.lbn13.x86_64
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.
Located in LBN / … / Core Linux / BastionLinux 13
libecap-0.2.0-4.fc18.armv6hl
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.
Located in LBN / … / Core Linux / BastionLinux 13
libecap-0.2.0-5.fc19.armv6hl
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.
Located in LBN / … / Core Linux / BastionLinux 19

« Previous 10 items Next 10 items » 1 ... 1127 1128 1129 1130 1131 1132 1133 ... 4849

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.