-
http-parser-2.0-4.20121128gitcd01361.fc19.x86_64
This is a parser for HTTP messages written in C. It parses both requests and
responses. The parser is designed to be used in performance HTTP applications.
It does not make any syscalls nor allocations, it does not buffer data, it can
be interrupted at anytime. Depending on your architecture, it only requires
about 40 bytes of data per message stream (in a web server that is per
connection).
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
http-parser-2.0-4.20121128gitcd01361.lbn13.x86_64
This is a parser for HTTP messages written in C. It parses both requests and
responses. The parser is designed to be used in performance HTTP applications.
It does not make any syscalls nor allocations, it does not buffer data, it can
be interrupted at anytime. Depending on your architecture, it only requires
about 40 bytes of data per message stream (in a web server that is per
connection).
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
http-parser-2.7.1-3.lbn25.x86_64
This is a parser for HTTP messages written in C. It parses both requests and
responses. The parser is designed to be used in performance HTTP applications.
It does not make any syscalls nor allocations, it does not buffer data, it can
be interrupted at anytime. Depending on your architecture, it only requires
about 40 bytes of data per message stream (in a web server that is per
connection).
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
http-parser-2.9.4-6.fc36.x86_64
This is a parser for HTTP messages written in C. It parses both requests and
responses. The parser is designed to be used in performance HTTP applications.
It does not make any syscalls nor allocations, it does not buffer data, it can
be interrupted at anytime. Depending on your architecture, it only requires
about 40 bytes of data per message stream (in a web server that is per
connection).
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
httpcomponents-client-4.5.2-4.fc25.noarch
HttpClient is a HTTP/1.1 compliant HTTP agent implementation based on
httpcomponents HttpCore. It also provides reusable components for
client-side authentication, HTTP state management, and HTTP connection
management. HttpComponents Client is a successor of and replacement
for Commons HttpClient 3.x. Users of Commons HttpClient are strongly
encouraged to upgrade.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
httpcomponents-client-4.5.2-4.lbn25.noarch
HttpClient is a HTTP/1.1 compliant HTTP agent implementation based on
httpcomponents HttpCore. It also provides reusable components for
client-side authentication, HTTP state management, and HTTP connection
management. HttpComponents Client is a successor of and replacement
for Commons HttpClient 3.x. Users of Commons HttpClient are strongly
encouraged to upgrade.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 25
-
httpcomponents-core-4.4.5-2.fc25.noarch
HttpCore is a set of low level HTTP transport components that can be
used to build custom client and server side HTTP services with a
minimal footprint. HttpCore supports two I/O models: blocking I/O
model based on the classic Java I/O and non-blocking, event driven I/O
model based on Java NIO.
The blocking I/O model may be more appropriate for data intensive, low
latency scenarios, whereas the non-blocking model may be more
appropriate for high latency scenarios where raw data throughput is
less important than the ability to handle thousands of simultaneous
HTTP connections in a resource efficient manner.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 19
-
httpcomponents-core-4.4.5-2.lbn25.noarch
HttpCore is a set of low level HTTP transport components that can be
used to build custom client and server side HTTP services with a
minimal footprint. HttpCore supports two I/O models: blocking I/O
model based on the classic Java I/O and non-blocking, event driven I/O
model based on Java NIO.
The blocking I/O model may be more appropriate for data intensive, low
latency scenarios, whereas the non-blocking model may be more
appropriate for high latency scenarios where raw data throughput is
less important than the ability to handle thousands of simultaneous
HTTP connections in a resource efficient manner.
Located in
LBN
/
…
/
Zenoss 4
/
BastionLinux 25
-
httpd-2.4.3-12.fc18.1302272148kf.armv6hl
The Apache HTTP Server is a powerful, efficient, and extensible
web server.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
httpd-2.4.6-2.fc19.armv6hl
The Apache HTTP Server is a powerful, efficient, and extensible
web server.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
