networking expert (as you can tell), so my terminology is probably
off.
An intermediary server in my case is not an option due to the
sensitive nature of my custumers' financial data, so it needs to be
some sort of "peer-to-peer" communincation.
I wonder if those "stickers" Google promised to retrofit phones for
Google Wallet would be usuable for general purpose NFC applications.
On May 30, 10:20 am, Bob Kerns <r...@acm.org> wrote:
> Android does support peer-to-peer wifi network, what exactly are you talking
> about? I suspect you mean something somewhat different. Ad hoc access
> points? You wouldn't want to do that anyway -- it would kill the user's
> active WiFi connection, and this isn't even remotely a legitimate
> application for ad hoc access points. (I'm not saying you couldn't establish
> one as a fallback - ad hoc networks are an ad hoc way of establishing
> connectivity when there's no regular access point. But that's at a lower
> level than an application; ad hoc networking is not an application-level
> feature). Peer-to-peer when not on the same subnet? That is entirely out of
> Android's hands; it can work, but you shouldn't expect it.
>
> If they're on the same subnet and can see each other (which depends on WiFi
> router configuration, *not* the Android), then you can communicate directly.
> If not, then try Bluetooth, otherwise, do what Bump appears to do -- send it
> via an intermediary server, which you can even do over 3G if there's no
> WiFi. If all else fails, you could display a 2D bar code on the sender's
> screen and let the receiver pick that up, and queue up the send and receive
> for later.
>
> But no, I'm not saying NFC would not be good for any particular application.
> I'm saying consider the limitations and see if it's a fit. A Bump-type comm
> would seem to me to be a good fit. Photo sync would in most cases not be,
> IMHO. A comm between a camera and a photo frame might be.
>
> But since NFC is not universally available, I'd currently consider it to be
> optional, and give development priority to Bluetooth and WiFi. But since it
> sets up quickly, once implemented, I'd try it first! Actually, I'd try to do
> the setup for the different transfer modes in parallel.
>
> Still you make a good point about it being easier than Bluetooth. I'd
> probably do WiFi first because it's easy and familiar and a higher priority
> product-wise, but NFC looks simple enough to be a reasonable choice of a
> starting point.
>
>
>
> On Sunday, May 29, 2011 2:28:35 AM UTC-7, Zsolt Vasvari wrote:
>
> > So are you saying the NFC would not be good for a Bump-type comm
> > between two devices? It just seems so much easier than pairing two
> > Bluetooth devices and since Android doesn't even support peer-to-peert
> > WIFI networking, that's completely out of the question.
>
> > On May 29, 9:13 am, Bob Kerns <r....@acm.org> wrote:
> > > Send? Just what do you think NFC is, exactly? It sounds like you think
> > it's
> > > an alternative to WiFi or Bluetooth. That's not exactly true, or only
> > > approximately true, depending on how you want to look at it.
>
> > > While in theory you could use it to communicate between two devices, the
> > > short range involved, and the low speed, make it less than attractive for
>
> > > this. If you Bluetooth or WiFi available, those would be much more
> > natural.
> > > So you may want to rethink whether this is the right tool for your job.
>
> > > Probably as a result, the activity I'm aware of is more around RFID tags
> > and
> > > various active readers. Probably there are people doing it, my point is
> > just
> > > that it doesn't seem to be terribly mainstream, and you may have trouble
> > > finding code samples.
>
> > > Yes, you'll have to divide it. The details are clearly laid out in the
> > NDEF
> > > standard document, which should only have taken you two minutes to
> > locate.
> > > That's how long it took me, anyway, starting from never having read any
> > > technical details on NFC. Really, I just entered NFC Tag into Google,
> > > clicked on Wikipedia, and clicked on this link from the Standards section
>
> > > there:
>
> > >http://www.nfc-forum.org/specs/
>
> > > <http://www.nfc-forum.org/specs/>See Section 2.3.3 of the NDEF spec.
>
> > > On Wednesday, May 25, 2011 5:10:56 AM UTC-7, ari...@hotmail.com wrote:
>
> > > > hi,
>
> > > > I do not think I explained myself well.
> > > > What I need is the code, so that when i take a photo with my mobile.
> > > > it bring me the option to send the picture by nfc.
> > > > thx
>
> > > > On 13 mayo, 17:28, cg-dev <charle...@gmail.com> wrote:
> > > > > Hi,
>
> > > > > As far as I know, I don't think you can put an image into a tag in a
> > > > > standard way.
> > > > > Check with Smart Poster Ndef tag type, maybe you can with this type.
>
> > > > > If only your application need to read and write the image, you can
> > > > > simply use Ndef type "Text" and put your image in a raw buffer.
>
> > > > > Regards.
>
> > > > > On 12 mai, 13:46, "ari...@hotmail.com" <ari...@hotmail.com> wrote:
>
> > > > > > Hi I asked for the code to send a photo with NFC without using a
> > web
> > > > > > page, if the records are 7ks we will have to divide it? or use
> > many,
> > > > > > or how can I do it?- Ocultar texto de la cita -
>
> > > > > - Mostrar texto de la cita -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment