Your programs? Are you sure you don't mean User Streams?

Tom


On 10/20/10 8:53 PM, Naoki Hiroshima wrote:
> Ok, maybe it's trivial in terms of the size of data sent from the
> server. But it seems taking a long time to receive all of those lists,
> and be ready to get status updates.
> If allowed, I'd like my programs to receive status updates as soon as
> they get connected.
> 
> -- @N
> 
> 
> 
> On Wed, Oct 20, 2010 at 9:20 AM, John Kalucki <j...@twitter.com> wrote:
>> This amount of data is trivial compared to the total amount of data sent
>> over Site Streams. The friends list per user is roughly the size of a tweet
>> or two. We have to weigh the cost of maintaining the feature vs. the
>> bandwidth and CPU savings. Unless the savings is significant, generally the
>> optimal solution is to let the client discard unneeded data.
>> -John
>>
>>
>>
>> On Tue, Oct 19, 2010 at 5:16 PM, N <n...@h7a.org> wrote:
>>>
>>> Hi there,
>>>
>>> I've been playing with Site Stream for a bit, and I have a request.
>>>
>>> When a client connects to the server, it returns a series of the
>>> friend list for each users. Can you make this optional? Receiving a
>>> lot of friends data for thousands of users is a quite bit of trafic
>>> and wasteful unless it's really needed. I'd be very happy if I
>>> wouldn't have to receive it when I don't need.
>>>
>>> --
>>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>>> API updates via Twitter: http://twitter.com/twitterapi
>>> Issues/Enhancements Tracker:
>>> http://code.google.com/p/twitter-api/issues/list
>>> Change your membership to this group:
>>> http://groups.google.com/group/twitter-development-talk
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>>
> 

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to