<?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: How Many Users Can Joomla Handle?</title>
	<atom:link href="http://www.itoctopus.com/how-many-users-can-joomla-handle/feed" rel="self" type="application/rss+xml" />
	<link>http://www.itoctopus.com/how-many-users-can-joomla-handle</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 22:17:19 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Why Joomla Is a Good Choice for Government Websites &#124; itoctopus</title>
		<link>http://www.itoctopus.com/how-many-users-can-joomla-handle/comment-page-1#comment-5221</link>
		<dc:creator>Why Joomla Is a Good Choice for Government Websites &#124; itoctopus</dc:creator>
		<pubDate>Wed, 12 Sep 2012 04:47:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.itoctopus.com/?p=433#comment-5221</guid>
		<description>[...] websites only receive a few thousand visits a day (at best) &#8211; which is well in the range of the number of users that Joomla can handle without scaling [...]</description>
		<content:encoded><![CDATA[<p>[...] websites only receive a few thousand visits a day (at best) &#8211; which is well in the range of the number of users that Joomla can handle without scaling [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joomla in Dubai &#124; itoctopus</title>
		<link>http://www.itoctopus.com/how-many-users-can-joomla-handle/comment-page-1#comment-3488</link>
		<dc:creator>Joomla in Dubai &#124; itoctopus</dc:creator>
		<pubDate>Tue, 27 Sep 2011 16:21:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.itoctopus.com/?p=433#comment-3488</guid>
		<description>[...] - Installing a Joomla website. The latest version of Joomla was required. - Modifying a Joomla 1.5 template to make it compatible with the 1.7 version of Joomla. - Securing the Joomla website for PCI certification (the website passed PCI certification the day we left Dubai). - Adding a product catalog and a shopping cart to the website, and integrating the checkout process with a payment gateway (non-PayPal). - Connecting the product catalog to the actual physical inventory of the supermarket (The challenge that faced us here is that since the databases are connected, what will happen when a user buys a product online that was physically bought (at the same time of the online transaction) by a shopper while visiting the actual store &#8211; the solution to this problem was to connect the database to another, non-displayed inventory, a technique that provided a better accuracy of the availability of the product, but a 100% accuracy was never guaranteed). - Alerting the user when his products are scheduled for delivery after he buys them from the website. - Creating and sending newsletters to website subscribers. - Automatically updating the Facebook fan page with the latest products (this took us a long time &#8211; but now we know how to do it) - Allowing users to watch a product. When a user watches a product, he will immediately receive an email when this product is on sale. - Allowing users to review/rate products. - Optimizing and scaling Joomla to handle thousands of daily investors (see our post on the number of users that Joomla can handle). [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; Installing a Joomla website. The latest version of Joomla was required. &#8211; Modifying a Joomla 1.5 template to make it compatible with the 1.7 version of Joomla. &#8211; Securing the Joomla website for PCI certification (the website passed PCI certification the day we left Dubai). &#8211; Adding a product catalog and a shopping cart to the website, and integrating the checkout process with a payment gateway (non-PayPal). &#8211; Connecting the product catalog to the actual physical inventory of the supermarket (The challenge that faced us here is that since the databases are connected, what will happen when a user buys a product online that was physically bought (at the same time of the online transaction) by a shopper while visiting the actual store &#8211; the solution to this problem was to connect the database to another, non-displayed inventory, a technique that provided a better accuracy of the availability of the product, but a 100% accuracy was never guaranteed). &#8211; Alerting the user when his products are scheduled for delivery after he buys them from the website. &#8211; Creating and sending newsletters to website subscribers. &#8211; Automatically updating the Facebook fan page with the latest products (this took us a long time &#8211; but now we know how to do it) &#8211; Allowing users to watch a product. When a user watches a product, he will immediately receive an email when this product is on sale. &#8211; Allowing users to review/rate products. &#8211; Optimizing and scaling Joomla to handle thousands of daily investors (see our post on the number of users that Joomla can handle). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
