Re: [twitter-dev] iPhone twitter streaming app

2010-02-16 Thread Carl Knott
Thanks for your reply. I will make those changes.

Currently, the user enters a search term, connects to the stream and
displays the results in a graphical manor. If the user decides to
search for something else, it disconnects the stream and reconnects
searching for a new keyword. I decided to use the streaming API
because I wanted real-time results. The only thing a user can do is
search for a term and view a user's tweet. Have I correctly used the
streaming API?

On Tue, Feb 16, 2010 at 4:05 AM, John Kalucki j...@twitter.com wrote:
 Carl,

 At this point, we are not encouraging end-user applications to communicate
 directly with the Streaming API. The primary purpose of the Streaming API is
 currently for service-to-service integrations. For example, we don't
 currently support oAuth.

 You may release your application, however. Each user must provide their
 credentials over basic auth. If everyone came in with your credentials,
 first, they'd probably be able to change your password and/or create spam on
 your account. Secondly, the Streaming API only allows one connection per
 account at a time. You'd only be able to support one user on your
 application -- yourself.

 -John Kalucki
 http://twitter.com/jkalucki
 Infrastructure, Twitter Inc.




 On Mon, Feb 15, 2010 at 2:47 AM, Carl Knott carl.kn...@gmail.com wrote:

 Hi, I've written a twitter steaming app that visualizes twitter search
 results. I am connecting to the stream using my own twitter account.
 Can I continue to use my own account when I release the application or
 would the user have to provide there own username/password? I want to
 be able to use my own account because its simpler and as the search
 results are public I don't want to limit the information to user's of
 twitter. Thank you, Carl.




Re: [twitter-dev] iPhone twitter streaming app

2010-02-16 Thread John Kalucki
Carl,

Yes, this is the purpose of the streaming api. We'd rather have all clients
on oAuth, but we're in transition, so this is fine for now. Also, for
capacity planning issues, we do not want large-scale end-user clients to
begin connecting to the Streaming API.

Just be sure that you've implemented the policies described in the wiki, and
double-checked the list at the end of the wiki, and you should be fine.

-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.





On Tue, Feb 16, 2010 at 1:01 AM, Carl Knott carl.kn...@gmail.com wrote:

 Thanks for your reply. I will make those changes.

 Currently, the user enters a search term, connects to the stream and
 displays the results in a graphical manor. If the user decides to
 search for something else, it disconnects the stream and reconnects
 searching for a new keyword. I decided to use the streaming API
 because I wanted real-time results. The only thing a user can do is
 search for a term and view a user's tweet. Have I correctly used the
 streaming API?

 On Tue, Feb 16, 2010 at 4:05 AM, John Kalucki j...@twitter.com wrote:
  Carl,
 
  At this point, we are not encouraging end-user applications to
 communicate
  directly with the Streaming API. The primary purpose of the Streaming API
 is
  currently for service-to-service integrations. For example, we don't
  currently support oAuth.
 
  You may release your application, however. Each user must provide their
  credentials over basic auth. If everyone came in with your credentials,
  first, they'd probably be able to change your password and/or create spam
 on
  your account. Secondly, the Streaming API only allows one connection per
  account at a time. You'd only be able to support one user on your
  application -- yourself.
 
  -John Kalucki
  http://twitter.com/jkalucki
  Infrastructure, Twitter Inc.
 
 
 
 
  On Mon, Feb 15, 2010 at 2:47 AM, Carl Knott carl.kn...@gmail.com
 wrote:
 
  Hi, I've written a twitter steaming app that visualizes twitter search
  results. I am connecting to the stream using my own twitter account.
  Can I continue to use my own account when I release the application or
  would the user have to provide there own username/password? I want to
  be able to use my own account because its simpler and as the search
  results are public I don't want to limit the information to user's of
  twitter. Thank you, Carl.