<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Weekly Contest: Push vs. Pull</title>
	<atom:link href="http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/</link>
	<description>The voice of the BlackBerry community.</description>
	<lastBuildDate>Wed, 22 May 2013 22:04:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: gun man</title>
		<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/comment-page-1/#comment-409075</link>
		<dc:creator>gun man</dc:creator>
		<pubDate>Wed, 23 Sep 2009 05:58:19 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/11/30/006166/#comment-409075</guid>
		<description><![CDATA[Well, This is a very interesting.. I will tell my friend and I&#039;m so sure that they will like this.]]></description>
		<content:encoded><![CDATA[<p>Well, This is a very interesting.. I will tell my friend and I&#8217;m so sure that they will like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gun man</title>
		<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/comment-page-1/#comment-487908</link>
		<dc:creator>gun man</dc:creator>
		<pubDate>Wed, 23 Sep 2009 05:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/11/30/006166/#comment-487908</guid>
		<description><![CDATA[Well, This is a very interesting.. I will tell my friend and I&#039;m so sure that they will like this.]]></description>
		<content:encoded><![CDATA[<p>Well, This is a very interesting.. I will tell my friend and I&#8217;m so sure that they will like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Frasca</title>
		<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/comment-page-1/#comment-213857</link>
		<dc:creator>Jason Frasca</dc:creator>
		<pubDate>Wed, 05 Dec 2007 00:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/11/30/006166/#comment-213857</guid>
		<description><![CDATA[The need for push is purely invented by RIM.  Their entire business model is based on the need for you to buy their enterprise server which makes them lots of dough.

You see, the iMap protocol [a pull protocol] does the exact same thing [from an e.mail perspective] and does it just as well, actually perhaps faster than the the RIM push.  I switched to the BB 8 months ago from the TREO 650... I had all my e.mail accounts on imap [2 domains mind you] and when I switched to BB I had to give up e.mail functionality for the great &quot;Push.&quot;  

Push is limited by microsoft excahnge  in many ways - sending e.mail from multiple addresses &amp; multiple domains for example which you can do with imap.  RIM did indeed spend a whole lot of money on their infrastructure and they bang you out for their BES licenses.

Look at BIS... 15 minute polling for POP3 access.... what a joke.  Why doesn&#039;t RIM support the imap protocol?  Becuase if they do they will wake their customers up to realizing how ripped off they are being taken for.  In this day and age we should not wait 15 mins for anything.  Plus, the 15 mins makes the &quot;Push&quot; service look so much more superior.  

Again, I purchased a piece of software on the Treo for $29.95 that supported imap that blew the BB e.mail client away.

Now, I must confess, the BB experience is much better than a Treo which is why I switched... plus I get instant contacts and calendar sync OTA... I recognize that... but that is not what the issue is here.

Rest assured RIM will never abandon push... if they do they will become an ordinary handset maker.]]></description>
		<content:encoded><![CDATA[<p>The need for push is purely invented by RIM.  Their entire business model is based on the need for you to buy their enterprise server which makes them lots of dough.</p>
<p>You see, the iMap protocol [a pull protocol] does the exact same thing [from an e.mail perspective] and does it just as well, actually perhaps faster than the the RIM push.  I switched to the BB 8 months ago from the TREO 650&#8230; I had all my e.mail accounts on imap [2 domains mind you] and when I switched to BB I had to give up e.mail functionality for the great &#8220;Push.&#8221;  </p>
<p>Push is limited by microsoft excahnge  in many ways &#8211; sending e.mail from multiple addresses &amp; multiple domains for example which you can do with imap.  RIM did indeed spend a whole lot of money on their infrastructure and they bang you out for their BES licenses.</p>
<p>Look at BIS&#8230; 15 minute polling for POP3 access&#8230;. what a joke.  Why doesn&#8217;t RIM support the imap protocol?  Becuase if they do they will wake their customers up to realizing how ripped off they are being taken for.  In this day and age we should not wait 15 mins for anything.  Plus, the 15 mins makes the &#8220;Push&#8221; service look so much more superior.  </p>
<p>Again, I purchased a piece of software on the Treo for $29.95 that supported imap that blew the BB e.mail client away.</p>
<p>Now, I must confess, the BB experience is much better than a Treo which is why I switched&#8230; plus I get instant contacts and calendar sync OTA&#8230; I recognize that&#8230; but that is not what the issue is here.</p>
<p>Rest assured RIM will never abandon push&#8230; if they do they will become an ordinary handset maker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Frasca</title>
		<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/comment-page-1/#comment-487907</link>
		<dc:creator>Jason Frasca</dc:creator>
		<pubDate>Wed, 05 Dec 2007 00:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/11/30/006166/#comment-487907</guid>
		<description><![CDATA[The need for push is purely invented by RIM.  Their entire business model is based on the need for you to buy their enterprise server which makes them lots of dough.

You see, the iMap protocol [a pull protocol] does the exact same thing [from an e.mail perspective] and does it just as well, actually perhaps faster than the the RIM push.  I switched to the BB 8 months ago from the TREO 650... I had all my e.mail accounts on imap [2 domains mind you] and when I switched to BB I had to give up e.mail functionality for the great &quot;Push.&quot;  

Push is limited by microsoft excahnge  in many ways - sending e.mail from multiple addresses &amp; multiple domains for example which you can do with imap.  RIM did indeed spend a whole lot of money on their infrastructure and they bang you out for their BES licenses.

Look at BIS... 15 minute polling for POP3 access.... what a joke.  Why doesn&#039;t RIM support the imap protocol?  Becuase if they do they will wake their customers up to realizing how ripped off they are being taken for.  In this day and age we should not wait 15 mins for anything.  Plus, the 15 mins makes the &quot;Push&quot; service look so much more superior.  

Again, I purchased a piece of software on the Treo for $29.95 that supported imap that blew the BB e.mail client away.

Now, I must confess, the BB experience is much better than a Treo which is why I switched... plus I get instant contacts and calendar sync OTA... I recognize that... but that is not what the issue is here.

Rest assured RIM will never abandon push... if they do they will become an ordinary handset maker.]]></description>
		<content:encoded><![CDATA[<p>The need for push is purely invented by RIM.  Their entire business model is based on the need for you to buy their enterprise server which makes them lots of dough.</p>
<p>You see, the iMap protocol [a pull protocol] does the exact same thing [from an e.mail perspective] and does it just as well, actually perhaps faster than the the RIM push.  I switched to the BB 8 months ago from the TREO 650&#8230; I had all my e.mail accounts on imap [2 domains mind you] and when I switched to BB I had to give up e.mail functionality for the great &#8220;Push.&#8221;  </p>
<p>Push is limited by microsoft excahnge  in many ways &#8211; sending e.mail from multiple addresses &amp; multiple domains for example which you can do with imap.  RIM did indeed spend a whole lot of money on their infrastructure and they bang you out for their BES licenses.</p>
<p>Look at BIS&#8230; 15 minute polling for POP3 access&#8230;. what a joke.  Why doesn&#8217;t RIM support the imap protocol?  Becuase if they do they will wake their customers up to realizing how ripped off they are being taken for.  In this day and age we should not wait 15 mins for anything.  Plus, the 15 mins makes the &#8220;Push&#8221; service look so much more superior.  </p>
<p>Again, I purchased a piece of software on the Treo for $29.95 that supported imap that blew the BB e.mail client away.</p>
<p>Now, I must confess, the BB experience is much better than a Treo which is why I switched&#8230; plus I get instant contacts and calendar sync OTA&#8230; I recognize that&#8230; but that is not what the issue is here.</p>
<p>Rest assured RIM will never abandon push&#8230; if they do they will become an ordinary handset maker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dzeims Balts</title>
		<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/comment-page-1/#comment-212848</link>
		<dc:creator>Dzeims Balts</dc:creator>
		<pubDate>Fri, 30 Nov 2007 20:49:15 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/11/30/006166/#comment-212848</guid>
		<description><![CDATA[It makes sense for the BlackBerry devices to continue using push.  The battery life issue is going to be the first obvious win for this kind of technology.  The bulk of usage for most BlackBerry devices are data service, and constantly polling for email, messages, updated web pages, etc is going to kill a battery quick.
The second obvious follow-up point will be that not everyone will have an unlimited data plan.  Push-based notifications to the BlackBerry device of email or other data will save money over polling, especially for BIS users who may not have their accounts/devices provided to them by their employers.  With GMail, Yahoo, Go Daddy and others joining with RIM to provide push-level BIS email notification, the otherwise push-lite BIS is making progress.
One of the more interesting points looking at the current tech space is that what BlackBerry devices can take for granted with push, the Web 2.0 crowd can only wish for in limited capacity.  &quot;Comet&quot;, essentially push for the AJAX browser level, is often judged as the solution to the needs and requirements for increasingly interactive Web 2.0 / AJAX web applications.  The only thing holding the Comet group back so far has been install-base adoption.  Here the BlackBerry infrastructure wins by virtue of having this from the beginning.
Finally, for all of those who consider BIS to be totally &quot;push-less&quot; or &quot;push-lite&quot; in capability, it was announced at the recent BlackBerry Virtual Tech Seminar that the free BlackBerry Unite would allow for push-based communication between it and its connected BlackBerry devices.]]></description>
		<content:encoded><![CDATA[<p>It makes sense for the BlackBerry devices to continue using push.  The battery life issue is going to be the first obvious win for this kind of technology.  The bulk of usage for most BlackBerry devices are data service, and constantly polling for email, messages, updated web pages, etc is going to kill a battery quick.<br />
The second obvious follow-up point will be that not everyone will have an unlimited data plan.  Push-based notifications to the BlackBerry device of email or other data will save money over polling, especially for BIS users who may not have their accounts/devices provided to them by their employers.  With GMail, Yahoo, Go Daddy and others joining with RIM to provide push-level BIS email notification, the otherwise push-lite BIS is making progress.<br />
One of the more interesting points looking at the current tech space is that what BlackBerry devices can take for granted with push, the Web 2.0 crowd can only wish for in limited capacity.  &#8220;Comet&#8221;, essentially push for the AJAX browser level, is often judged as the solution to the needs and requirements for increasingly interactive Web 2.0 / AJAX web applications.  The only thing holding the Comet group back so far has been install-base adoption.  Here the BlackBerry infrastructure wins by virtue of having this from the beginning.<br />
Finally, for all of those who consider BIS to be totally &#8220;push-less&#8221; or &#8220;push-lite&#8221; in capability, it was announced at the recent BlackBerry Virtual Tech Seminar that the free BlackBerry Unite would allow for push-based communication between it and its connected BlackBerry devices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dzeims Balts</title>
		<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/comment-page-1/#comment-487906</link>
		<dc:creator>Dzeims Balts</dc:creator>
		<pubDate>Fri, 30 Nov 2007 20:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/11/30/006166/#comment-487906</guid>
		<description><![CDATA[It makes sense for the BlackBerry devices to continue using push.  The battery life issue is going to be the first obvious win for this kind of technology.  The bulk of usage for most BlackBerry devices are data service, and constantly polling for email, messages, updated web pages, etc is going to kill a battery quick.
The second obvious follow-up point will be that not everyone will have an unlimited data plan.  Push-based notifications to the BlackBerry device of email or other data will save money over polling, especially for BIS users who may not have their accounts/devices provided to them by their employers.  With GMail, Yahoo, Go Daddy and others joining with RIM to provide push-level BIS email notification, the otherwise push-lite BIS is making progress.
One of the more interesting points looking at the current tech space is that what BlackBerry devices can take for granted with push, the Web 2.0 crowd can only wish for in limited capacity.  &quot;Comet&quot;, essentially push for the AJAX browser level, is often judged as the solution to the needs and requirements for increasingly interactive Web 2.0 / AJAX web applications.  The only thing holding the Comet group back so far has been install-base adoption.  Here the BlackBerry infrastructure wins by virtue of having this from the beginning.
Finally, for all of those who consider BIS to be totally &quot;push-less&quot; or &quot;push-lite&quot; in capability, it was announced at the recent BlackBerry Virtual Tech Seminar that the free BlackBerry Unite would allow for push-based communication between it and its connected BlackBerry devices.]]></description>
		<content:encoded><![CDATA[<p>It makes sense for the BlackBerry devices to continue using push.  The battery life issue is going to be the first obvious win for this kind of technology.  The bulk of usage for most BlackBerry devices are data service, and constantly polling for email, messages, updated web pages, etc is going to kill a battery quick.<br />
The second obvious follow-up point will be that not everyone will have an unlimited data plan.  Push-based notifications to the BlackBerry device of email or other data will save money over polling, especially for BIS users who may not have their accounts/devices provided to them by their employers.  With GMail, Yahoo, Go Daddy and others joining with RIM to provide push-level BIS email notification, the otherwise push-lite BIS is making progress.<br />
One of the more interesting points looking at the current tech space is that what BlackBerry devices can take for granted with push, the Web 2.0 crowd can only wish for in limited capacity.  &#8220;Comet&#8221;, essentially push for the AJAX browser level, is often judged as the solution to the needs and requirements for increasingly interactive Web 2.0 / AJAX web applications.  The only thing holding the Comet group back so far has been install-base adoption.  Here the BlackBerry infrastructure wins by virtue of having this from the beginning.<br />
Finally, for all of those who consider BIS to be totally &#8220;push-less&#8221; or &#8220;push-lite&#8221; in capability, it was announced at the recent BlackBerry Virtual Tech Seminar that the free BlackBerry Unite would allow for push-based communication between it and its connected BlackBerry devices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bla1ze</title>
		<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/comment-page-1/#comment-212754</link>
		<dc:creator>Bla1ze</dc:creator>
		<pubDate>Fri, 30 Nov 2007 14:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/11/30/006166/#comment-212754</guid>
		<description><![CDATA[haha!! ya that comment was priceless, thnxs Simon.]]></description>
		<content:encoded><![CDATA[<p>haha!! ya that comment was priceless, thnxs Simon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bla1ze</title>
		<link>http://www.blackberrycool.com/2007/11/30/weekly-contest-push-vs-pull/comment-page-1/#comment-487905</link>
		<dc:creator>Bla1ze</dc:creator>
		<pubDate>Fri, 30 Nov 2007 14:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://blackberrycool.com/2007/11/30/006166/#comment-487905</guid>
		<description><![CDATA[haha!! ya that comment was priceless, thnxs Simon.]]></description>
		<content:encoded><![CDATA[<p>haha!! ya that comment was priceless, thnxs Simon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
