>> > I don't see why everyone who is using BK is expecting Linus to do a pull.
>> > In the non-BK case, wasn't it always a "push" model, and Linus would not
>> > "pull" from URLs and such?
>> I'm all for it. I think it's a good thing.
>> In the absence of significant latency issues, pull scales better than push.
>> It always has. Push is better in low bandwidth situations with lots of idle
>> capacity, but it breaks down when the system approaches saturation.
>> Pull data is naturally supplied when you're ready for it (assuming no
>> significant latency to access it). Push either scrolls by unread or piles up
>> in your inbox and gets buried until it goes stale. Web pages work on a pull
>> model, "push" was an internet fad a few years ago that failed for a reason.
>> When push models hit saturation it breaks down and you wind up with the old
>> "I love lucy" episode with the chocolate factory. Back in the days where
>What's "i love lucy" episode?
"I Love Lucy" was a 1950s sitcom on television, one of the first and
very good indeed.
In the episode referred to, Lucy and her friend Ethel get hired as
candy-packers in a candy factory. The candies come by on a conveyer
belt and the girls put them in boxes. Everything went smoothly... the
manager reviewed the situation, and congratulated them. Then they
increased the conveyer belt flow. After a few more cycles, the candy
was coming too fast. So they started taking the candies, stuffing them
into pockets, blouses, mouths... and the scene ends with the manager
arriving back madder then heck.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/