From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WLbea-0006Ij-CW for bitcoin-development@lists.sourceforge.net; Thu, 06 Mar 2014 17:00:16 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.174 as permitted sender) client-ip=209.85.220.174; envelope-from=mh.in.england@gmail.com; helo=mail-vc0-f174.google.com; Received: from mail-vc0-f174.google.com ([209.85.220.174]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WLbeZ-00048U-69 for bitcoin-development@lists.sourceforge.net; Thu, 06 Mar 2014 17:00:16 +0000 Received: by mail-vc0-f174.google.com with SMTP id im17so2890922vcb.33 for ; Thu, 06 Mar 2014 09:00:05 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.52.122.14 with SMTP id lo14mr1029363vdb.38.1394125205520; Thu, 06 Mar 2014 09:00:05 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.52.24.38 with HTTP; Thu, 6 Mar 2014 09:00:05 -0800 (PST) In-Reply-To: References: Date: Thu, 6 Mar 2014 18:00:05 +0100 X-Google-Sender-Auth: nSEI9QqjVagPWs9AZ0iZ7IbEwGw Message-ID: From: Mike Hearn To: Andreas Schildbach Content-Type: multipart/alternative; boundary=089e013a1b22a5c64004f3f31173 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WLbeZ-00048U-69 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Instant / contactless payments, IsoDep X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2014 17:00:16 -0000 --089e013a1b22a5c64004f3f31173 Content-Type: text/plain; charset=UTF-8 I think maybe the way you do it is to have a NDEF tag that triggers the app, and then that starts an IsoDep protocol once opened. I *think*. On Thu, Mar 6, 2014 at 5:55 PM, Andreas Schildbach wrote: > 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. > > > > > > ------------------------------------------------------------------------------ > Subversion Kills Productivity. Get off Subversion & Make the Move to > Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and > the > freedom to use Git, Perforce or both. Make the move to Perforce. > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --089e013a1b22a5c64004f3f31173 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I think maybe the way you do it is to have a NDEF tag that= triggers the app, and then that starts an IsoDep protocol once opened. I *= think*.


= On Thu, Mar 6, 2014 at 5:55 PM, Andreas Schildbach <andreas@schildbach= .de> wrote:
On 03/06/2014 03:51 PM, Andreas Schildbach w= rote:

>> =C2=A0 =C2=A0 I'm not sure if iso-dep is the way to go here. A= faik as soon as you pick
>> =C2=A0 =C2=A0 up the phone the connection breaks.
>>
>> If the phone isn't willing to immediately authorise then it= 9;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=3Dandroid.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.




---------------------------------------------------------------------------= ---
Subversion Kills Productivity. Get off Subversion & Make the Move to Pe= rforce.
With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. =C2=A0Built-in WAN optimization = and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D122218951&iu=3D/4140/ostg.clktrk
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--089e013a1b22a5c64004f3f31173--