There's no need to open a connection per user. You should demultiplex
the messages from a single connection or from a very small number of
connections. See
http://groups.google.com/group/twitter-development-talk/browse_frm/thread/4090d5a49bf32a2e/545d9d9c5a662a41?lnk=gst&q=hash#545d9d9c5a662a41

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

On Nov 18, 2:46 pm, briantroy <brian.cosin...@gmail.com> wrote:
> I have a question about the streaming API.
>
> I am currently whitelisted for the standard search API on several IP
> addresses. I'd like to begin moving to the streaming API (at least to
> test) but am blocked by the "one connection per account" limit.
>
> Is there a way to be whitelisted (by IP or credentials) to have
> multiple connections? Is the assumed methodology that I would create a
> single "stream" for 100's or 1000's of clients and somehow figure out
> on my side which track term goes with which client?
>
> Any help would be appreciated.
>
> regards,
>
> Brian Roy
> justSignal.com

Reply via email to