Right, that makes sense, so let’s not join them. The alternate thing to do is to create a
contact on sign up, because if you want to receive push notifications at least you should
be in the list of contacts. We will still need to change the sign up page a little as we
need a phone number and a birth date as well in order to create a contact.
On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter(a)redhat.com> wrote:
These are not strongly held opinions
One reason to keep Users & Contacts separate is...because that is normal for the
average enterprise app - your have employees (users) and customers (contacts) -
employees/users have different roles/privileges from customers.
The reason they are separated in the secured (PL) version of contacts-mobile-basic is
because it simply evolved that way - contacts came first - users/roles added after the
fact. Ideally we would not modify the original too much as it allows a nice learning
progression - start with the original contacts-mobile-basic, then upgrade to
contacts-mobile-basic-secured, then upgrade to contacts-mobile-basic-secured-cordova
(names just made up).
On Apr 23, 2014, at 10:16 AM, Sébastien Blanc <scm.blanc(a)gmail.com> wrote:
> Sure !
> Be sure to check this with Joshua as he drives the backend bits
> Envoyé de mon iPhone
>> Le 23 avr. 2014 à 15:56, Erik Jan de Wit <edewit(a)redhat.com> a écrit :
>> How about merging the User model and the Contact into one entity? Seems like they
have a lot in common, do we really need 2?
>> Erik Jan
>>> On 23 Apr,2014, at 14:34 , Sébastien Blanc <scm.blanc(a)gmail.com>
>>> We should be using the email as alias and the email should also be used as
login when registering in the secured part. A registration should also trigger the
creation of that user / contact in the application.
>>> Author can be left empty By the client and filled by the backend .
stay because the receiver must know who sends the message.
>>> Envoyé de mon iPhone
>>>> Le 23 avr. 2014 à 13:35, Erik Jan de Wit <edewit(a)redhat.com> a
>>>> I was working on the aerogear-push-quickstarts for Cordova and was
wondering what to put for the alias on registration. The version that is there now has
users that logs in and contacts that are fetched. What seems to be missing is that
everybody gets all contacts instead of just mine (maybe that is fine), but users that sign
up for the app are not contacts. So when I want to send a message to a specific mobile
user they are not in my list and there is no way to have to define an alias to send to.
>>>> Also the interface for sending push notifications includes a author. I
think it would be better if we remove this and let the service put in the logged in user.
That way you can’t pretend to send a message like someone else.
>>>> What do you think?
>>>> Erik Jan
>>>> aerogear-dev mailing list
>>> aerogear-dev mailing list
>> aerogear-dev mailing list
> aerogear-dev mailing list
aerogear-dev mailing list