Note: The Streaming API is currently under a limited alpha test,
details below.

Multiple concurrent connections from the same account are discouraged
on the Streaming API. Starting on or after the afternoon of Monday,
May 11th (22:00:00 11-May-2009 UTC) the service will gently enforce
this policy. A later release will fully enforce this policy.
Subsequent connections from the same account will cause previously
established connections to be disconnected.

In some cases, this might cause operational difficulties for
developers who are using the restricted resources. For example, a
developer's staging test might knock that developer's production /
gardenhose feed offline. Non-production uses should connect to the /
spritzer resource with a secondary account to avoid these conflicts.
We may, on a case-by-case basis, grant exceptions to this policy as we
work through the alpha test. We will attempt to balance ease-of-use,
resource consumption and abuse prevention.

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



Important Alpha Test Note:
The Streaming API (aka Hosebird) is currently under an alpha test. All
developers using the Streaming API must tolerate possible unannounced
and extended periods of unavailability, especially during off-hours,
Pacific Time. New features, resources and policies are being deployed
on very little, if any, notice. Any developer may experiment with the
unrestricted resources and provide feedback via this list. Access to
restricted resources is extremely limited and is only granted on a
case-by-case basis after acceptance of an additional terms of service
document. Documentation is available: 
http://apiwiki.twitter.com/Streaming-API-Documentation.

Reply via email to