ubuntu-push-devs team mailing list archive

[Ted Gould <ted@xxxxxxxxxx>]

Let me try to rephrase so that I'm sure I understand.  I'm going to use
IRC terminology because I don't see a better vocab, and I'm reasonably
sure everyone understands it :-)

Every developer has a nick connected to the server (which is
authenticated) and every device has a nick that is connected to the
server (which is authenticated).  There are applications, and each of
these has a chat room.  The developers are admins of these rooms, and
every device that has the app installed is connected to that room.  If
the developer wants to send something to everyone who has the app
installed, they can put something in the chat room and everyone sees it.
Sometimes, they'll want a query to send to a specific device.  The
developer needs to be able to get a list of everyone in the chat room to
know who to query, but also get notified when people join/leave the room
to keep their query list up-to-date.

Is that a fair restatement?

Ted

On Thu, 2013-08-08 at 12:05 -0300, Lucio Torre wrote:
> Yes, although thats something that could be made to work, that not an
> important use case.
> 
> 
> 
> But my point was more around the "notify developer that he needs to
> send stuff to the app"
> 
> 
> Having the Server contact the developer to alter the subscription
> status seems like we are adding more API than what we need.
> 
> 
> The key issue here is that the developer does not push to the
> application. He pushes to the user-device-application. So he needs to
> be notified of every install/uninstall by us.
> 
> 
> I think that in the long run all apps will talk to their developers to
> agree on something, so trying to capture that seems too much work.
> 
> 
> Lucio.
> 
> 
> 
> On Thu, Aug 8, 2013 at 11:46 AM, Ted Gould <ted@xxxxxxxxxx> wrote:
> 
>         On Thu, 2013-08-08 at 10:59 -0300, Lucio Torre wrote: 
>         
>         > On Thu, Aug 8, 2013 at 10:00 AM, Ted Gould <ted@xxxxxxxxxx>
>         > wrote:
>         > 
>         >         I'm not sure what you're meaning here by token.  It
>         >         seems like you don't need tokens as much as you need
>         >         to authenticate everyone connecting, and keep a list
>         >         of what they're allow to see and/or post.  I don't
>         >         think they need to be tokens of any type as long as
>         >         everyone authenticates to the server where the lists
>         >         are stored.
>         >         
>         > 
>         > Tokens are just a way to do that without having to keep a
>         > list of everyone that could be posting. The app-3rdparty
>         > communication still needs to happen so the 3rd party needs
>         > it needs to start notifying the app. 
>         
>         
>         
>         
>         Perhaps, I'm confused a bit on what problem we're trying to
>         solve.  I figured we were looking at something like this:
>         
>         
>         
>         Which seems like the only auth is that the developer is
>         allowed to push to any application that he/she also own.  And
>         then the device can filter out specific application pushes.
>         
>         Are you saying that the use-cases are more like this though?
>         
>         
>         I'm not sure how apps would really use that.  Do you have any
>         use-cases there?
>         
>         Thanks,
>         Ted
>         
>         
>         --
>         Mailing list: https://launchpad.net/~ubuntu-push-devs
>         Post to     : ubuntu-push-devs@xxxxxxxxxxxxxxxxxxx
>         Unsubscribe : https://launchpad.net/~ubuntu-push-devs
>         More help   : https://help.launchpad.net/ListHelp
>         
> 
> 
>

Attachment: signature.asc
Description: This is a digitally signed message part