You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hc.apache.org by se...@apache.org on 2013/07/26 14:20:20 UTC
svn commit: r1507281 - in /httpcomponents/httpcore/trunk: BUILDING.txt
doap_HttpComponents_Core.rdf
Author: sebb
Date: Fri Jul 26 12:20:20 2013
New Revision: 1507281
URL: http://svn.apache.org/r1507281
Log:
Trailing spaces tidyup
Modified:
httpcomponents/httpcore/trunk/BUILDING.txt
httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf
Modified: httpcomponents/httpcore/trunk/BUILDING.txt
URL: http://svn.apache.org/viewvc/httpcomponents/httpcore/trunk/BUILDING.txt?rev=1507281&r1=1507280&r2=1507281&view=diff
==============================================================================
--- httpcomponents/httpcore/trunk/BUILDING.txt (original)
+++ httpcomponents/httpcore/trunk/BUILDING.txt Fri Jul 26 12:20:20 2013
@@ -1,4 +1,4 @@
-Building HttpComponents Core
+Building HttpComponents Core
============================
(1) Requisites
@@ -6,7 +6,7 @@ Building HttpComponents Core
JDK 1.5+ is required in order to compile and run HttpCore.
HttpCore utilizes Maven as a distribution management and packaging tool.
-Version 3.0.3 or later is required.
+Version 3.0.3 or later is required.
Maven installation and configuration instructions can be found here:
@@ -18,9 +18,9 @@ Execute the following command in order t
mvn test
-(3) Building packages
+(3) Building packages
-Execute the following command in order to build the JAR packages and install
+Execute the following command in order to build the JAR packages and install
them to the local repository:
mvn install
@@ -33,7 +33,7 @@ httpcore-osgi/target/org.apache.httpcomp
where <VERSION> is the release version
-(4) Building documentation
+(4) Building documentation
Execute the following command in order to generate javadoc:
Modified: httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf
URL: http://svn.apache.org/viewvc/httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf?rev=1507281&r1=1507280&r2=1507281&view=diff
==============================================================================
--- httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf (original)
+++ httpcomponents/httpcore/trunk/doap_HttpComponents_Core.rdf Fri Jul 26 12:20:20 2013
@@ -1,8 +1,8 @@
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl"?>
<rdf:RDF xml:lang="en"
- xmlns="http://usefulinc.com/ns/doap#"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns="http://usefulinc.com/ns/doap#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:asfext="http://projects.apache.org/ns/asfext#"
xmlns:foaf="http://xmlns.com/foaf/0.1/">
<!--
@@ -47,11 +47,11 @@ including support for NIO.
</shortdesc>
<description>
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
+ 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.
</description>
<bug-database rdf:resource="http://issues.apache.org/jira/browse/HTTPCORE" />