Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of m.gmane.org
	designates 80.91.229.3 as permitted sender)
	client-ip=80.91.229.3;
	envelope-from=gcbd-bitcoin-development@m.gmane.org;
	helo=plane.gmane.org; 
To: bitcoin-development@lists.sourceforge.net
From: Andreas Schildbach <andreas@schildbach.de>
Date: Thu, 06 Mar 2014 17:55:53 +0100
Message-ID: <lfa9ab$k1c$1@ger.gmane.org>
References: <CANEZrP3w9c_UX3dd+7LdWNXCEwjnAG+bYWxqKYo_fzakWQu=Bg@mail.gmail.com>	<lf9m0e$q7t$1@ger.gmane.org>	<CANEZrP2GbnsqQANGKMW_5FAugppGJEksaB=Tf8Xu1nRLy3z9yg@mail.gmail.com>
	<lfa20f$i2k$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
In-Reply-To: <lfa20f$i2k$1@ger.gmane.org>
Subject: Re: [Bitcoin-development] Instant / contactless payments, IsoDep
Precedence: list

On 03/06/2014 03:51 PM, Andreas Schildbach wrote:

>>     I'm not sure if iso-dep is the way to go here. Afaik as soon as you pick
>>     up the phone the connection breaks.
>>
>> If the phone isn't willing to immediately authorise then it'd have to
>> fall back to HTTPS or Bluetooth as normal.
> 
> Ok, that would be an option.

One of the first things to explore is if its possible to dispatch
different isodep applications to different apps. I know you can add an
intent filter matching action=android.nfc.action.TECH_DISCOVERED and a
custom "tech filter" android.nfc.tech.IsoDep. However, as long as there
is no mime type or similar concept, apps will always fight for access to
IsoDep endpoints. We will want to avoid that situation.