Jump to content

Adding additional users to a session


Luke

Recommended Posts

These two endpoints will allow you to do that

 

    [Route("/Sessions/{Id}/Users/{UserId}", "POST")]
    [Route("/Sessions/{Id}/Users/{UserId}", "DELETE")]
 
This way when something is watched for that session, the playstate goes to every user.
 
Eventually I'll have the web client do some neat tricks with it so that you can see what's possible for mobile. But living room clients can use it to mimic the new netflix functionality where you can indicate who else is present in the room.
Link to comment
Share on other sites

CBers

How does this work from a user point of view?

 

Do we have to tell MB3 who is viewing somehow?

 

TIA.

Link to comment
Share on other sites

gcw07

How does this work from a user point of view?

 

Do we have to tell MB3 who is viewing somehow?

 

TIA.

At the moment there is no user point of view. It is just an API end point at the moment. I would assume eventually you would be able to sign in a person and then sign in another as just "viewing". It would just then mark things. This would all depend upon the client. Hopefully one day we can also have a feature built into the server where "X" user can always be attached to the view state of "Y" user.

  • Like 1
Link to comment
Share on other sites

Redshirt

It's going to be a little while before this gets to Android. Unless other client dev's force my hand :) 

 

 

CBers. Client devs will need to provide a sign-in UI indicating to the end user that they are 'also signing in, or out' user x. There will also need to be indicators in the client to remind the user that more than one user is signed in. As it will have an impact on things like Trakt that actually do stuff with the watch status.

  • Like 1
Link to comment
Share on other sites

Redshirt

It's too early for me to say but the I may go the route gcw07 suggested on the client side where we have a user-group entitiy and add various users to it so that it's a simple fact of selecting the group rather than manually signing in each user.

  • Like 1
Link to comment
Share on other sites

It's going to be a little while before this gets to Android. Unless other client dev's force my hand :)

 

 

CBers. Client devs will need to provide a sign-in UI indicating to the end user that they are 'also signing in, or out' user x. There will also need to be indicators in the client to remind the user that more than one user is signed in. As it will have an impact on things like Trakt that actually do stuff with the watch status.

 

 

and that is good you have bigger and better things to do right now. it's initially for mbc.

Link to comment
Share on other sites

How about adding it to the system info call?  I don't currently have a result on the authentication post.

Link to comment
Share on other sites

That doesn't really have anything to do with system info. i can add filters to the sessions endpoint so that you can get it based device info, but i'll also add it to the auth result because there is an object that comes back on that call.

Link to comment
Share on other sites

chef

@@chef can probably use this

 

This sounds like another step, filling in the blanks, towards programmatic user switching.

 

Plus, kinect will enumerate faces and can automatically load the user names who are watching.

 

This could be very cool, if I can make it work that way.

Link to comment
Share on other sites

  • 2 weeks later...
Redshirt

I'll get a release build out in the next few days. Clearly ebr is sitting on a cool feature he wants to release.

Link to comment
Share on other sites

Are there any changes to login that we would need to make? Assuming we aren't wanting to implement the multiple user stuff yet, is there anything that would break existing login?

Link to comment
Share on other sites

you just need to make sure you're always sending the identification header, even when you don't yet have a user id. just omit that value from the string. if you're already doing that then you're fine.

Link to comment
Share on other sites

  • 2 weeks later...
Redshirt

The client changes needed to send the author header for everything have been made in the current android public release.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...