Yes, that sounds similar to what i do.
- i created a custom auth user table, it happens to be called end_user
(though it can be called auth_user):
auth.settings.table_user_name = 'end_user'
auth.settings.table_user = db.end_user.table
auth.define_tables()
- My end_user t
Thanks for all the interesting responses.
Here is Apple's description of the Push notificaiton process:
http://developer.apple.com/library/mac/#documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ApplePushService/ApplePushService.html
There appears to be a similar framework for
Hmm; good point.
On Wed, Feb 13, 2013 at 4:30 AM, howesc wrote:
> for our system we have "anonymous" users (users with no email address), and
> "known" users (users with an email address.
>
> Apple does not expose the MAC address, the IMEI or the apple UDID of iOS
> devices to developers. their
for our system we have "anonymous" users (users with no email address), and
"known" users (users with an email address.
Apple does not expose the MAC address, the IMEI or the apple UDID of iOS
devices to developers. their policies strictly forbid the use of hardware
identifiers in apps distrib
On Tue, Feb 12, 2013 at 4:29 AM, howesc wrote:
> Thanks Alec, that will be a nice contribution.
>
> re my "special odd pain in the rear-end" login flow.well we (the
> engineers) failed to sell that to the business. users can make purchases
> via apple without a proper logged in account, and w
Thank you, guys. :) I think I should try to implement one, when I am free.
Do you know any opensource for iphone oauth login as well as android?
I am actually passing login credentials to web2py from android app via
given web2py lib.
On Feb 11, 2013 11:29 AM, "howesc" wrote:
> Thanks Alec, tha
Thanks Alec, that will be a nice contribution.
re my "special odd pain in the rear-end" login flow.well we (the
engineers) failed to sell that to the business. users can make purchases
via apple without a proper logged in account, and we need to track those on
the server. hence the anonym
Not to worry, I'm releasing a generalised open-source OAuth2 Library for web2py.
As for your current mechanism of anonymous tokens… how about just
storing a cookie (or some other client-side storage) and when the user
logs-in or registers all their customisations (e.g.: if e-commerce,
their cart)
- Apple explicitly does not allow using the hardware identifier in your
app, and will reject app submission that do that. because of this each app
install "logs in" first as an anonymous user.
- website users use standard web2py auth
- app connections to the server use our modified OAuth API
Howesc,
Thanks for great info. So, does mobile app user have to register web2py via
access token provided by their hardware in mobile application? May you
explain how you built the login/registration module for mobile app users
along with web2py?
Do you code in html5 with native code for developing
well what we are using is a hybrid model:
- the ios device uses a modified form of OAuth to get access tokens (and
we have the confusing problem of users start anonymous but with an access
token, and then may later create an "account" associating an email and
other user data with the account)
I do not know how this works. Can you give us more details?
On Friday, 8 February 2013 20:31:14 UTC-6, howesc wrote:
>
> i have millions of APNS tokens! i'd share, but they are tied to an app
>
> i did not tie APNS tokesn to web2py auth, but i added fields to my end
> user table, and the devi
i have millions of APNS tokens! i'd share, but they are tied to an app
i did not tie APNS tokesn to web2py auth, but i added fields to my end user
table, and the device uses my REST JSON API to POST the APNS tokens to the
server and update the user. we don't use the APNS token as any sort o
13 matches
Mail list logo
