Once the service fully enforces the intended policy, then yes, a / spritzer login will knock off a /gardenhose login, or visa versa. The current intention is for developers to create a /gardenhose production account and a testing /spritzer account. At first glance, this requirement does not appear too onerous. Unfortunately such clients will require the login credentials to be predicated on production status.
If we're missing a use case, let's discuss. We have options at this early stage. -John Kalucki - Services, Twitter Inc. http://twitter.com/jkalucki On May 10, 12:55 pm, benburkert <b...@benburkert.com> wrote: > Just to clarify, are we limited to one resource per account? If i > connect to /spritzer on a test server, will that knock off my > connection to /gardenhose on my production server if I use the same > account? > > -Ben > > On May 9, 11:04 pm, John Kalucki <jkalu...@gmail.com> wrote: > > > 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.
