Hi all~
I youtube the Roku and have a try of Joseph Smarr's tutorial about NF API...
I think there exist some differences between them..
1) About the authorization...
>>>Roku ： Only need to sign up a serial number to activate Netflix ready device once..
>>>NF API： Have to authorise the access token each time developer want to access user's resource..
[Question] Is there a different way Roku implement the Authorization. Or some API not release to developer testing?
Because I don't see people have to go on internet to authorise the access token each time he wana read his instant queue.
2) About the player...
>>>Roku ： Watch movie directly on the device without browser. ( It doesn't have browser, right? Or I misunderstand? )
>>>NF API： Java Script, Browser, Flash player ( Abode-Flash / MS-SilverLight? ).
[Question] If wana instant watch on a device without browser. What do I need? Flash player only? If so how can it receive the streaming video.
Is there any information about the streaming protocol and video/audio codec format of instant queue films?
~~~~~~~~~~~~~~~~~~Thanks for reply!!~~~~~~~~~~
In regards to your first question, if I'm understanding correctly, it looks as if you misunderstand how the access tokens work. Once the user has authorized the access token, you can save that and use it forever. The only way that access token will cease to work is if the user manually de-authorizes your application from accessing their account. So, to answer your question, the Roku doesn't do anything special, it just saves the authenticated access token/secret for future use.
Now, as for your second question, I'm actually looking for an answer to that one as well. So if you figure anything out, please post it here so we can benefit from your knowledge :)
The instant watching streaming service isn't supported by this API today. There is another private API for CE partners that supports that, but you have to get through our biz dev team to get into the program due to the higher costs of integration, certification, etc. The bar is pretty high.
That's for your response. I know that information is helpful for me, and I hope it is helpful for koax2 as well. Do you have a contact in the "biz dev team" over there that we should get in touch with regarding this? Any help would be greatly appreciated.
Try sending an email to alliances at our domain name dot com. We get tons of partnership requests around instant watching and the engagement cost per partner is quite high, even during the biz dev phase so make a really strong case with your first email. You're competing for cycles with partners like Samsung, LG, XBOX, etc.
Hi all~
I youtube the Roku and have a try of Joseph Smarr's tutorial about NF API...
I think there exist some differences between them..
1) About the authorization...
>>>Roku ： Only need to sign up a serial number to activate Netflix ready device once..
>>>NF API： Have to authorise the access token each time developer want to access user's resource..
[Question] Is there a different way Roku implement the Authorization. Or some API not release to developer testing?
Because I don't see people have to go on internet to authorise the access token each time he wana read his instant queue.
2) About the player...
>>>Roku ： Watch movie directly on the device without browser. ( It doesn't have browser, right? Or I misunderstand? )
>>>NF API： Java Script, Browser, Flash player ( Abode-Flash / MS-SilverLight? ).
[Question] If wana instant watch on a device without browser. What do I need? Flash player only? If so how can it receive the streaming video.
Is there any information about the streaming protocol and video/audio codec format of instant queue films?
~~~~~~~~~~~~~~~~~~Thanks for reply!!~~~~~~~~~~
Message edited by kaox2 3 years ago
ReQuest Inc – 3 years ago
In regards to your first question, if I'm understanding correctly, it looks as if you misunderstand how the access tokens work. Once the user has authorized the access token, you can save that and use it forever. The only way that access token will cease to work is if the user manually de-authorizes your application from accessing their account. So, to answer your question, the Roku doesn't do anything special, it just saves the authenticated access token/secret for future use.
Now, as for your second question, I'm actually looking for an answer to that one as well. So if you figure anything out, please post it here so we can benefit from your knowledge :)
Brian
Michael Hart – 3 years ago
The instant watching streaming service isn't supported by this API today. There is another private API for CE partners that supports that, but you have to get through our biz dev team to get into the program due to the higher costs of integration, certification, etc. The bar is pretty high.
ReQuest Inc – 3 years ago
Michael-
That's for your response. I know that information is helpful for me, and I hope it is helpful for koax2 as well. Do you have a contact in the "biz dev team" over there that we should get in touch with regarding this? Any help would be greatly appreciated.
Michael Hart – 3 years ago
Try sending an email to alliances at our domain name dot com. We get tons of partnership requests around instant watching and the engagement cost per partner is quite high, even during the biz dev phase so make a really strong case with your first email. You're competing for cycles with partners like Samsung, LG, XBOX, etc.
kaox2 – 3 years ago
Michael-
Thanks for replying. It's helpful.
ReQuest Inc-
Thanks for your comment, It's helpful,too.
Aaron Alexander – 3 years ago
is this streaming api available yet? if not can i get a contact to apply to this private api?
Michael Hart – 3 years ago
Aaron, read two posts up.