<?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: BlazeDS vs LiveCycleDS</title>
	<atom:link href="http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/</link>
	<description>News and Information about Adobe Flex &#38; Adobe AIR by Rich Tretola</description>
	<lastBuildDate>Thu, 11 Mar 2010 05:16:12 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Asep</title>
		<link>http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/comment-page-1/#comment-50730</link>
		<dc:creator>Asep</dc:creator>
		<pubDate>Tue, 26 May 2009 07:17:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/#comment-50730</guid>
		<description>We would like to nominate you for a FreedomToBlog.com Best of Blog Entry.

Please visit our site at: http://www.freedomtoblog.com to submit your blog entry!

Benefits include: 
1) Permanent Backlinks to your blog
2) Fully SEO optimized for maximum exposure
3) A chance to be published into a top 500 best of blog book&quot;</description>
		<content:encoded><![CDATA[<p>We would like to nominate you for a FreedomToBlog.com Best of Blog Entry.</p>
<p>Please visit our site at: <a href="http://www.freedomtoblog.com" rel="nofollow">http://www.freedomtoblog.com</a> to submit your blog entry!</p>
<p>Benefits include:<br />
1) Permanent Backlinks to your blog<br />
2) Fully SEO optimized for maximum exposure<br />
3) A chance to be published into a top 500 best of blog book&quot;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: everythingflex</title>
		<link>http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/comment-page-1/#comment-567</link>
		<dc:creator>everythingflex</dc:creator>
		<pubDate>Tue, 08 Jul 2008 11:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/#comment-567</guid>
		<description>No yet, but what we are testing is not a single server. It will be a cluster.</description>
		<content:encoded><![CDATA[<p>No yet, but what we are testing is not a single server. It will be a cluster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niraj Sonar</title>
		<link>http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/comment-page-1/#comment-570</link>
		<dc:creator>Niraj Sonar</dc:creator>
		<pubDate>Mon, 07 Jul 2008 07:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/#comment-570</guid>
		<description>Hi,

Have you got the results of load testing. Can you share the same with us for concurrent users. I want to know how many concurrent users can be supported by blazeDS in single instance. Can we scale it up for further ?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Have you got the results of load testing. Can you share the same with us for concurrent users. I want to know how many concurrent users can be supported by blazeDS in single instance. Can we scale it up for further ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: everythingflex</title>
		<link>http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/comment-page-1/#comment-568</link>
		<dc:creator>everythingflex</dc:creator>
		<pubDate>Thu, 26 Jun 2008 08:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/#comment-568</guid>
		<description>We are getting ready to do some load testing next week on a multi-server BlazeDS architecture so the results will soon show themselves.</description>
		<content:encoded><![CDATA[<p>We are getting ready to do some load testing next week on a multi-server BlazeDS architecture so the results will soon show themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andy matthews</title>
		<link>http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/comment-page-1/#comment-569</link>
		<dc:creator>andy matthews</dc:creator>
		<pubDate>Thu, 26 Jun 2008 00:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/#comment-569</guid>
		<description>I spoke with Adam Lehman at Webmaniacs this year and he specifically said that use of LCDS for a production app (even with a multi-proc server) was &quot;okay with Adobe&quot; unless your app was expected to have hundreds of concurrent users. Blaze can handle around 500 at a time, whereas LCDS is 10 times that (5000 plus).

He even stated to me &quot;I&#039;d even be willing to put that in an email&quot;. So take that as you will.</description>
		<content:encoded><![CDATA[<p>I spoke with Adam Lehman at Webmaniacs this year and he specifically said that use of LCDS for a production app (even with a multi-proc server) was &#8220;okay with Adobe&#8221; unless your app was expected to have hundreds of concurrent users. Blaze can handle around 500 at a time, whereas LCDS is 10 times that (5000 plus).</p>
<p>He even stated to me &#8220;I&#8217;d even be willing to put that in an email&#8221;. So take that as you will.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

