From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Instant / contactless payments, IsoDep
Date: Thu, 06 Mar 2014 17:55:53 +0100 [thread overview]
Message-ID: <lfa9ab$k1c$1@ger.gmane.org> (raw)
In-Reply-To: <lfa20f$i2k$1@ger.gmane.org>
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.
next prev parent reply other threads:[~2014-03-06 16:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:45 [Bitcoin-development] Instant / contactless payments Mike Hearn
2014-03-06 11:26 ` Andreas Schildbach
2014-03-06 13:44 ` Mike Hearn
2014-03-06 14:51 ` Andreas Schildbach
2014-03-06 16:55 ` Andreas Schildbach [this message]
2014-03-06 17:00 ` [Bitcoin-development] Instant / contactless payments, IsoDep Mike Hearn
2014-03-07 8:45 ` Andreas Schildbach
2014-03-07 9:26 ` [Bitcoin-development] Instant / contactless payments Johannes Zweng
2014-03-07 10:00 ` Mike Hearn
2014-03-07 10:23 ` Andreas Schildbach
2014-03-07 11:01 ` Mike Hearn
2014-03-07 12:00 ` Johannes Zweng
2014-03-06 14:20 ` Brooks Boyd
2014-03-06 17:07 ` Mike Hearn
2014-03-06 18:08 ` Brooks Boyd
2014-03-06 18:12 ` Mike Hearn
2014-03-06 18:20 ` Brooks Boyd
2014-03-06 18:24 ` Mike Hearn
2014-03-07 18:07 ` Joel Kaartinen
2014-03-06 14:39 ` Alex Kotenko
2014-03-06 16:46 ` Andreas Schildbach
2014-03-06 16:52 ` Mike Hearn
2014-03-06 18:03 ` Alex Kotenko
2014-03-07 8:59 ` Andreas Schildbach
2014-03-06 17:03 ` Mike Hearn
2014-03-06 18:49 ` Alex Kotenko
2014-03-08 8:52 ` Jan Vornberger
2014-03-10 15:09 ` Alex Kotenko
2014-03-10 19:28 ` Andreas Schildbach
2014-03-10 19:47 ` Alex Kotenko
2014-03-07 19:08 ` Troy Benjegerdes
2014-03-10 16:04 ` Mike Hearn
2014-03-10 16:14 ` Jean-Paul Kogelman
2014-03-10 16:27 ` Alex Kotenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lfa9ab$k1c$1@ger.gmane.org' \
--to=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox