Comments on: Push or Pull? Stateless or Stateful? http://blog.semergence.com/2007/08/28/push-or-pull-stateless-or-stateful/ Seth Ladd's blog about Ruby on Rails and crunching data. Sat, 10 Jan 2009 03:06:04 +0000 http://wordpress.org/?v=MU hourly 1 By: sethladd http://blog.semergence.com/2007/08/28/push-or-pull-stateless-or-stateful/#comment-234 sethladd Mon, 03 Sep 2007 18:19:28 +0000 http://204.14.242.104/?p=633#comment-234 <p>When I'm on vacation, I certainly don't want any feeds pushed to me. :) So in either case, I'm going offline. In a Push world, the server (or content provider) is responsible for maintaining the state of which events I've received and buffering the rest. That doesn't seem too scalable.</p> <p>Also, in the Pull model, when I get back from vacation, I can easily control the flow of old events as I pull at the rate I'm comfortable. In the Push model, there would have to be some protocol elements that helped control flow (rate).</p> When I’m on vacation, I certainly don’t want any feeds pushed to me. :) So in either case, I’m going offline. In a Push world, the server (or content provider) is responsible for maintaining the state of which events I’ve received and buffering the rest. That doesn’t seem too scalable.

Also, in the Pull model, when I get back from vacation, I can easily control the flow of old events as I pull at the rate I’m comfortable. In the Push model, there would have to be some protocol elements that helped control flow (rate).

]]> By: Stelios Sfakianakis http://blog.semergence.com/2007/08/28/push-or-pull-stateless-or-stateful/#comment-233 Stelios Sfakianakis Mon, 03 Sep 2007 13:29:46 +0000 http://204.14.242.104/?p=633#comment-233 <p>"The more Push events I have, the less I get done, the less I can focus, and the more transient everything becomes. To get things done, I need to Pull information when I’m good and ready."</p> <p>What makes you believe that Pull is more appropriate for doing more and more efficiently? Taking syndication as an example of a traditional Pull application, imagine that you go offline for vacations and after 2 weeks you get back: Are you sure that you are "good and ready" to manage the Pulled information from a large number of feeds (or email)?</p> <p>Also Pull/Push can be combined in some interesting scenarios: email is Push as far as the sender in concerned but Pull for the receiver. You can also have email-to-im bridges or instant messages stored in a database and retrieved by Pull for some "enterprise" scenarios...</p> “The more Push events I have, the less I get done, the less I can focus, and the more transient everything becomes. To get things done, I need to Pull information when I’m good and ready.”

What makes you believe that Pull is more appropriate for doing more and more efficiently? Taking syndication as an example of a traditional Pull application, imagine that you go offline for vacations and after 2 weeks you get back: Are you sure that you are “good and ready” to manage the Pulled information from a large number of feeds (or email)?

Also Pull/Push can be combined in some interesting scenarios: email is Push as far as the sender in concerned but Pull for the receiver. You can also have email-to-im bridges or instant messages stored in a database and retrieved by Pull for some “enterprise” scenarios…

]]> By: David Illsley http://blog.semergence.com/2007/08/28/push-or-pull-stateless-or-stateful/#comment-232 David Illsley Wed, 29 Aug 2007 11:13:27 +0000 http://204.14.242.104/?p=633#comment-232 <p>"If I’m not actively maintaining an open connection, can the system still be called Push?" - IMO yes, as long as I can open a connection to you and push information at you.</p> “If I’m not actively maintaining an open connection, can the system still be called Push?” - IMO yes, as long as I can open a connection to you and push information at you.

]]>