<?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: ABAP Freak Show &#8211; June 3rd &#8211; Web Dynpro ABAP Notification Service</title>
	<atom:link href="http://enterprisegeeks.com/blog/2009/06/03/abap-freak-show-june-3rd-web-dynpro-abap-notification-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://enterprisegeeks.com/blog/2009/06/03/abap-freak-show-june-3rd-web-dynpro-abap-notification-service/</link>
	<description></description>
	<lastBuildDate>Fri, 11 May 2012 19:30:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Thomas Jung</title>
		<link>http://enterprisegeeks.com/blog/2009/06/03/abap-freak-show-june-3rd-web-dynpro-abap-notification-service/comment-page-1/#comment-3773</link>
		<dc:creator>Thomas Jung</dc:creator>
		<pubDate>Sun, 13 Nov 2011 22:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://enterprisegeeks.com/blog/?p=1217#comment-3773</guid>
		<description>@Wolfgang: there is a balance here between network usage and impact on the server side.  The requests are processed by the ICM Cache, as you say, and therefore don&#039;t need to drop in to the ABAP layer for processing. Without extensive new development in the ICM to sleep the server thread or dropping into an ABAP work process and sleeping; this was our workaround.  Development felt that the network impact of the ICM check was small enough, but it is something you can consider when using this feature. One thing planned for the future is the ability for the application to set the polling interval and therefore perhaps set a timing of several seconds.  A small change in the interval might not even be noticeable to the end user, but could have a significant impact to the network traffic.</description>
		<content:encoded><![CDATA[<p>@Wolfgang: there is a balance here between network usage and impact on the server side.  The requests are processed by the ICM Cache, as you say, and therefore don&#8217;t need to drop in to the ABAP layer for processing. Without extensive new development in the ICM to sleep the server thread or dropping into an ABAP work process and sleeping; this was our workaround.  Development felt that the network impact of the ICM check was small enough, but it is something you can consider when using this feature. One thing planned for the future is the ability for the application to set the polling interval and therefore perhaps set a timing of several seconds.  A small change in the interval might not even be noticeable to the end user, but could have a significant impact to the network traffic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wolfgang Röckelein</title>
		<link>http://enterprisegeeks.com/blog/2009/06/03/abap-freak-show-june-3rd-web-dynpro-abap-notification-service/comment-page-1/#comment-3769</link>
		<dc:creator>Wolfgang Röckelein</dc:creator>
		<pubDate>Thu, 10 Nov 2011 21:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://enterprisegeeks.com/blog/?p=1217#comment-3769</guid>
		<description>When using CL_WD_NOTIFICATION_SERVICE (eg. from the demo application WDR_TEST_NOTIFICATION), the browser sends each second a request to /sap/public/bc/webdynpro/Polling which is answered immediatly (from ICM cache).

IMHO this hardly counts as &quot;long polling&quot;, &quot;comet&quot;-equivalent or the like since the idea there is that the browser opens one connection which the server keeps open until a result needs to be communicated.

The problem with the current approach is that this transmitts about 300bytes each second which would make it 1 MegaByte in a hour!

Does anybody have an idea how to circumvent this problem?</description>
		<content:encoded><![CDATA[<p>When using CL_WD_NOTIFICATION_SERVICE (eg. from the demo application WDR_TEST_NOTIFICATION), the browser sends each second a request to /sap/public/bc/webdynpro/Polling which is answered immediatly (from ICM cache).</p>
<p>IMHO this hardly counts as &#8220;long polling&#8221;, &#8220;comet&#8221;-equivalent or the like since the idea there is that the browser opens one connection which the server keeps open until a result needs to be communicated.</p>
<p>The problem with the current approach is that this transmitts about 300bytes each second which would make it 1 MegaByte in a hour!</p>
<p>Does anybody have an idea how to circumvent this problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ameya Suvarna</title>
		<link>http://enterprisegeeks.com/blog/2009/06/03/abap-freak-show-june-3rd-web-dynpro-abap-notification-service/comment-page-1/#comment-3219</link>
		<dc:creator>Ameya Suvarna</dc:creator>
		<pubDate>Wed, 29 Dec 2010 11:40:15 +0000</pubDate>
		<guid isPermaLink="false">http://enterprisegeeks.com/blog/?p=1217#comment-3219</guid>
		<description>Amazing features and easy to work with... Just blew away my OLTP reporting nightmare in Web Dynpro... Thanks!!!</description>
		<content:encoded><![CDATA[<p>Amazing features and easy to work with&#8230; Just blew away my OLTP reporting nightmare in Web Dynpro&#8230; Thanks!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

