draft-laugstol-apache-maven-repository-rest-applications-02.txt		draft-laugstol-apache-maven-repository-rest-applications-03.txt
	skipping to change at page 1, line 46		skipping to change at page 1, line 46
	Table of Contents		Table of Contents
	1. TODOs and Notes . . . . . . . . . . . . . . . . . . . . . . . 2		1. TODOs and Notes . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2		2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
	2.1. Goals: . . . . . . . . . . . . . . . . . . . . . . . . . . 2		2.1. Goals: . . . . . . . . . . . . . . . . . . . . . . . . . . 2
	2.2. Implementation goals . . . . . . . . . . . . . . . . . . . 3		2.2. Implementation goals . . . . . . . . . . . . . . . . . . . 3
	2.3. Areas explicitly not covered . . . . . . . . . . . . . . . 3		2.3. Areas explicitly not covered . . . . . . . . . . . . . . . 3
	2.4. Deployment scenarios . . . . . . . . . . . . . . . . . . . 3		2.4. Deployment scenarios . . . . . . . . . . . . . . . . . . . 3
	3. Specification . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Specification . . . . . . . . . . . . . . . . . . . . . . . . 3
	3.1. Media Types . . . . . . . . . . . . . . . . . . . . . . . 3		3.1. Media Types . . . . . . . . . . . . . . . . . . . . . . . 3
	3.2. Operations . . . . . . . . . . . . . . . . . . . . . . . . 4		3.2. Operations . . . . . . . . . . . . . . . . . . . . . . . . 3
	3.3. Uploading Artifacts . . . . . . . . . . . . . . . . . . . 4		3.3. Uploading Artifacts . . . . . . . . . . . . . . . . . . . 4
	3.4. Downloading Artifacts . . . . . . . . . . . . . . . . . . 4		3.4. Downloading Artifacts . . . . . . . . . . . . . . . . . . 4
	3.4.1. Download a single artifact . . . . . . . . . . . . . . 4		3.4.1. Download a single artifact . . . . . . . . . . . . . . 4
	3.4.2. Download a set of artifacts . . . . . . . . . . . . . 5		3.4.2. Download a set of artifacts . . . . . . . . . . . . . 4
	3.5. Searching . . . . . . . . . . . . . . . . . . . . . . . . 5		3.5. Searching . . . . . . . . . . . . . . . . . . . . . . . . 5
	4. Protocol Bindings . . . . . . . . . . . . . . . . . . . . . . 5		4. Protocol Bindings . . . . . . . . . . . . . . . . . . . . . . 5
	4.1. Response Bindings . . . . . . . . . . . . . . . . . . . . 5		4.1. Response Bindings . . . . . . . . . . . . . . . . . . . . 5
	5. Security Aspects . . . . . . . . . . . . . . . . . . . . . . . 5		5. Security Aspects . . . . . . . . . . . . . . . . . . . . . . . 5
	5.1. Authentication and Authorization . . . . . . . . . . . . . 5		5.1. Authentication and Authorization . . . . . . . . . . . . . 5
	6. User-Agent Considerations . . . . . . . . . . . . . . . . . . 5		6. User-Agent Considerations . . . . . . . . . . . . . . . . . . 5
	7. HTTP Binding . . . . . . . . . . . . . . . . . . . . . . . . . 5		7. HTTP Binding . . . . . . . . . . . . . . . . . . . . . . . . . 5
	8. Appendix: Words and Definitions . . . . . . . . . . . . . . . 5		8. Appendix: Words and Definitions . . . . . . . . . . . . . . . 5
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 6		9. Security Considerations . . . . . . . . . . . . . . . . . . . 6
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	skipping to change at page 2, line 53		skipping to change at page 2, line 53
	+ There are both a standalone XML format and a HTTP binding		+ There are both a standalone XML format and a HTTP binding
	that can be used. It might be feasible to include metalink		that can be used. It might be feasible to include metalink
	inside atom and possibly metalink inside collection+JSON		inside atom and possibly metalink inside collection+JSON
	2. Introduction		2. Introduction
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	View Source
	2.1. Goals:		2.1. Goals:
	o Any user agent should be able to rely on caching information given		o Any user agent should be able to rely on caching information given
	by the repository. No explicit caching should be necessary by the		by the repository. No explicit caching should be necessary by the
	application using a user agent for a Maven repository. In other		application using a user agent for a Maven repository. In other
	words, no ~/.m2/repository or ~/.ivy2.		words, no ~/.m2/repository or ~/.ivy2.
	o It should be possible to use standard HTTP intermediates without		o It should be possible to use standard HTTP intermediates without
	interfering. This is required to cover several use cases:		interfering. This is required to cover several use cases:
End of changes. 3 change blocks.
	3 lines changed or deleted		2 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/