commit bb33a340755bcd10179f2428ebd8cd866dc89eba
parent 75c9c754c8af74cbfdede1736751c3ae3bbb208a
Author: Florian Dold <florian.dold@gmail.com>
Date: Tue, 12 Jan 2016 15:42:35 +0100
delete old wallet spec
Diffstat:
2 files changed, 0 insertions(+), 17 deletions(-)
diff --git a/index.rst b/index.rst
@@ -64,8 +64,6 @@ interfaces between the core components of Taler.
api-mint
api-merchant
- wallet
-
wireformats
diff --git a/wallet.rst b/wallet.rst
@@ -9,21 +9,6 @@ this componenet - one browser based and the other implemented as an `app` for mo
General
-------
-Mints and merchants have a base URL for their service. This URL *must* be in a
-canonical form when it is stored (e.g. in the wallet's database) or transmitted
-(e.g. to a bank page).
-
-1. The URL must be absolute. This implies that the URL has a schema.
-2. The path component of the URL must end with a slash.
-3. The URL must not contain a fragment or query.
-
-When a user enters a URL that is, technically, relative (such as "alice.example.com/mint"), wallets
-*may* transform it into a canonical base URL ("http://alice.example.com/mint/"). Other components *should not* accept
-URLs that are not canonical.
-
-Rationale: Joining non-canonical URLs with relative URLs (e.g. "mint.example.com" with "reserve/status")
-results in different and slightly unexpected behavior in some URL handling libraries.
-Canonical URLs give more predictable results with standard URL joining.
---------------
Error Handling
