Using the Client
Nope. We're just doing this for fun. This project is not associated with Netflix.
Right now your best bet is emailing one of the developers. We're also working on getting an issue tracker up.
Most practically, it shields you from having to worry about OAuth much. Creating and signing requests, exchanging request tokens for access tokens, et. al., gets pretty tedious after a while. We've taken care of that.
Actually, you can get an
InputStream back as well. By default, calling
getResponse() returns a string,
because in the vast majority of cases, that's all that anyone will ever want or need. If you call
getResponseStream() though, you'll get a stream... handy for those humongous calls to
All our documentation assumes you're familiar with REST in general and Netflix's use of it in particular, all of which is covered nicely by the offical docs.
The three-part OAuth handshake is necessary to get access to user data without getting their credentials. This can only be done by sending the user to the Netflix site to log in and authorize your application to act on their behalf. Netflix will then redirect the user back to your site to continue with your use case. Obviously, for this to happen, your app needs to be able to listen for HTTP traffic. But that's OAuth, which was from the beginning conceived as a web protocol. Embedded apps and devices need to use another means of obtaining access tokens, which is not covered by this library.
Note that obtaining user's credentials, even with their permission, is directly and explicitly against the Netflix API TOS. In short, doing so may get you busted, and booted from the developer network, so don't do this!