None of this is Cocoa related
take it off the list immediately
On 2009-07-24, at 7:36 AM, Jesse Armand wrote:
I suppose mobile banking is less secure than regular internet
banking ?
I'm not sure what is the weakness in mobile banking, compared to
regular internet banking, where both of the
On 24 Jul 2009, at 12:36, Jesse Armand wrote:
I suppose mobile banking is less secure than regular internet
banking ?
I'm not sure what is the weakness in mobile banking, compared to
regular internet banking, where both of them have a secure device to
generate code for transactions ?
Let's s
I suppose mobile banking is less secure than regular internet banking ?
I'm not sure what is the weakness in mobile banking, compared to
regular internet banking, where both of them have a secure device to
generate code for transactions ?
Let's say somebody stole your phone, what can he/she do wi
Roland hello.
Thanks for the advises, I think I will stick with the reply SMS-> save
my app status-> close my app -> (hit the link of the sms if comes with
url, or copy the access code and relaunch my app)-> complete the
authentication with the access code.
well, if that;s they way to d
Well you can't register to listen to SMSes, that hook just doesn't
exist. So if you rely on proving who someone is by sending something to
a specific phone (ie making use of the telephone companys vast network
ability to locate one device with that particular SIM card in it at that
point in tim
You should look into the push notification API, it ends up being very
similar to SMS (e.g. small payloads) and is directly developer
accessible.
->Ben
--
Ben Lachman
Acacia Tree Software
http://acaciatreesoftware.com
email: blach...@mac.com
twitter: @benlachman
mobile: 740.590.0009
On Ju
I have been there before, for a mobile banking project, and they don't
want to accept my suggestion to process all of the sms processing
(incoming / outgoing) on the server, in order for the iPhone app to
communicate with server only.
That would provide better user experience, because there's no n
@ Jesse:
Yes the idea is to distribute the App through the AppStore, so I guess
I can't go any deeper.
The idea is that in the server there is gonna be a sms application
that will send the Authorization code to the registered iPhone that is
asking for it, then My app should take that acce
Right, but you can register your own url schemes which will launch
your app and let it handle the data. I've assumed that the SMS
displaying framework will parse out such URLs, realize they are
registered and put the correct hotlink into the message to launch your
app.
On Jul 23, 2009, a
The sms: URL on the iPhone only supports phone number, unless if
you're willing to go deep into the private API, but you couldn't
distribute your app into the App Store.
My advice is, better to install some kind of sms application or
gateway on your server, so your iPhone app could send the text i
Nop you didn\'t miss understood the question, I will have a look at
the docs, because the idea is that once Im in my app, put the first
credentials, then the server will send me an authorizaiton code, and
the idea is to don't leave my app to get the data from the sms, but
the app fetch the
If you're trying to use data which has been sms'ed to your user, which
is something I've thought about doing before, the only way which I
thought it could be done is to register your own url for the application
and then have the sms you send include the data in a URL format, eg if
your app regi
Aha ok.. thanks.
I need to develop an iPhone app that fetches sms data form the sender,
the data are access keys, so I was wondering if tis possible to do
such an application.
I was reading the iPhone App programing Guide, and there is something
interesting, I can register my app with so
13 matches
Mail list logo
