Alexy, First, curl isn't the best approach for developing against the Streaming API. It's fine for prototyping, but it only goes so far.
Yes, the comma separated list should be all on one line if you are using curl. If you want to change the user set, you should connect with the new set and then disconnect the old set immediately once the data starts to flow. This will be hard to coordinate using curl. In some cases, Twitter will throw the first user off once the second user connects. In other cases it will be more lenient. But, beware: if you want to avoid running into various abuse limits, you'd best be sure that your coordination between the first and second streams are quite solid and that the first stream is always terminated in a timely manner. You can also avoid data loss by using the count parameter, available on some, but not all, methods. Please email me with your use case and I'll forward it on to the Platform PM to help prioritize the better solution, as outlined by Alex. -John Kalucki twitter.com/jkalucki Services, Twitter Inc. On Jul 8, 12:17 pm, braver <[email protected]> wrote: > Uf you have thousands of users, do you really have to cook up a > following file with comma-separated say 100,000 user IDs? Should it > all be on one line? Now what happens if we want to drop some and add > some IDs -- do we have to restart and re-upload all that list again? > I see when the curl -d @following ... starts up, it does that. > Restarting with huge lists sounds like data loss... > > Cheers, > Alexy
