<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Silicon Valley Web Hosting Blog &#187; Web Hosting</title>
	<atom:link href="http://blog.svwh.net/category/web-hosting/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.svwh.net</link>
	<description>Web Hosting News and Articles</description>
	<lastBuildDate>Thu, 02 Jul 2009 08:30:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to implement downloads through PHP with resumption and multi-stream capability</title>
		<link>http://blog.svwh.net/web-hosting/how-to-implement-downloads-through-php-with-resumption-and-multi-stream-capability/</link>
		<comments>http://blog.svwh.net/web-hosting/how-to-implement-downloads-through-php-with-resumption-and-multi-stream-capability/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 08:30:32 +0000</pubDate>
		<dc:creator>div</dc:creator>
				<category><![CDATA[Web Hosting]]></category>

		<guid isPermaLink="false">http://blog.svwh.net/web-hosting/how-to-implement-downloads-through-php-with-resumption-and-multi-stream-capability/</guid>
		<description><![CDATA[In present web programming practice there often arises the task of implementing downloads through PHP (or other scripting languages). The task itself is not very hard. PHP includes the function virtual() which can be used for this purpose. But this realization has one problem: there is no way to resume aborted downloads and no way [...]]]></description>
			<content:encoded><![CDATA[<p>In present web programming practice there often arises the task of implementing downloads through PHP (or other scripting languages). The task itself is not very hard. PHP includes the function virtual() which can be used for this purpose. But this realization has one problem: there is no way to resume aborted downloads and no way to download files in a multi-stream manner. Below you will find a sample PHP code which solves these problems. But, let’s start with some theory behind the code.First of all we should discuss the mechanism of how this behavior works. This functionality is a part of HTTP 1.1 standart RFC2616 (see w3c specification: <a title="RFC2616" href="http://www.w3.org/Protocols/rfc2616/rfc2616.html">http://www.w3.org/Protocols/rfc2616/rfc2616.html</a> ).</p>
<p>So as we can see from the specifications in the RFC document, resuming and multi-streaming download support is mostly handled by following HTTP headers: “Content-Length” and “Content-Range”. Additionally response status header “HTTP/1.1 206 Partial Content” defined for this type of requests/responses. First download request is no different from standard request. The main “magic” will begin with subsequent requests, when user (specifically the user web browser/download client) requests download resumption or the next part of multi-stream download. The users’ client sends to the web server a request with supplied position to determine where it wants to start the download. Commonly this position is equal to where the download was aborted. Also, by using this functionality, most download clients organize multi-streamed downloading through sending to the server a few requests at the same time, so multi-streamed downloading technically is the same thing as resumption of download.</p>
<p>After web server receives such a request, it should answer either with standard status “200″, what in fact means “download resumption is not supported” (this is how the implementation of virtual() function works), or after handling received data, server should reply with “206″ status code, content length, content range, and, of course, content itself. All this functionality is supported by default in most recent HTTP servers, but as said above, sometimes this content should be given to client through a PHP script (for example after authorization).</p>
<p><a title="handle_file_download.php " href="http://ks.svwh.net/downloads/handle_file_download.php.tar.bz2">handle_file_download.php.tar.bz2</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.svwh.net/web-hosting/how-to-implement-downloads-through-php-with-resumption-and-multi-stream-capability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SSD: Fact or Friction</title>
		<link>http://blog.svwh.net/web-hosting/ssd-fact-or-friction/</link>
		<comments>http://blog.svwh.net/web-hosting/ssd-fact-or-friction/#comments</comments>
		<pubDate>Tue, 05 May 2009 13:22:40 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Web Hosting]]></category>

		<guid isPermaLink="false">http://blog.svwh.net/web-hosting/ssd-fact-or-friction/</guid>
		<description><![CDATA[SSD and the Future
We stand poised on the brink of yet another paradigm shift in technology. This shift will be in the form of a simple device that most of us have a love/hate relationship with. This device I speak of is the internal Hard Drive, yes you heard me. For the last 24 years [...]]]></description>
			<content:encoded><![CDATA[<p><strong>SSD and the Future</strong></p>
<p>We stand poised on the brink of yet another paradigm shift in technology. This shift will be in the form of a simple device that most of us have a love/hate relationship with. This device I speak of is the internal Hard Drive, yes you heard me. For the last 24 years there has been no better media to store our prized data on than the spinning magneto platters that have grown from such simple beginnings as the 5MB hard disk made up of 50 two foot diameter magnetic disks or platters to today&#8217;s 1.5TB (that&#8217;s Terabytes to you and me, 1500 Gigabytes) 3.5 inch hard drive found in modern desktop and server platforms.</p>
<p>With a variety of interfaces that have spawned ever increasing speeds and opened up the door to new applications never dreamed of when storage required 200lbs of spinning metal to store only a few Megabytes of information, let&#8217;s not even talk about seek times. From early Bus connectors we arrived at the first standard storage connector known as IDE (Integrated Drive Electronics)and the SCSI or &#8220;scuzzy&#8221; (Small Computer System Interface) adapter was soon to follow with increased performance and longevity finally followed by the Serial adapters in the forms of SATA (Serial Advanced Technology Attachment) and SAS or Serial Attached SCSI which use the same connector types but different controllers and have become the newest standard in manufacturing and data storage connectivity.</p>
<p>Over the years we have seen seek times steadily dropping from &#8220;Let&#8217;s go get a cup of coffee while this file opens&#8221; measured best in minutes to the blistering 9ms (that&#8217;s milliseconds) of the modern 15k RPM SCSI drives, ear plugs not included. And with each successive increase in speed came and equally compelling desire to reduce cost and increase the speed even further until today we can purchase at any corner store or delicatessen a hard drive with 250+ GB of storage and an average seek time of sub 20ms for less than $.30 per Gigabyte.</p>
<p><strong>How you ask, does this relate to some Paradigm shift?</strong></p>
<p>Enter the SSD or Solid State Drive, no longer a disk, this data storage device has no moving parts and is nearly as exciting to look at as a brick. Let me quickly rewind to 2004 when I was first introduced to the world of SSD. At this time we at Silicon Valley Web Hosting were looking for a solution to a customer&#8217;s request for higher levels of data delivery. It seems that they were not happy with the SCSI RAID configuration that we had built them 2 years before and wanted to explore some other options for increasing their performance. Enter BitMicro http://www.bitmicro.com/ a pioneer in SSD technology that could deliver us a whopping 8GB of storage in the convenient form of an 80 pin 3.5&#8243; SCSI drive for a mere $4500 each. These drives had a seek time at or below 1ms which was extraordinary even for SSD at the time and based on some preliminary testing I was able to determine that these drives would definitely relieve the bottle neck that our customer was seeing.</p>
<p>Alas, we could not justify the 30x increase in cost that this storage solution required and the plans for implementing SSD in our environment were shelved for another day. Fast forward to 2009 and we now see SSD being adopted on the desktop, sold in Laptops from Dell, HP, ASUS and many other manufacturers with seeming wide acceptance (and a few hiccups). Today a simple Google search for SSD returns thousands of hits for drives ranging in size and cost of 8GB for $70 to 512GB for $2000 from makers like OCZ, Transcend, Super Talent,  and here is where the shift is taking place. In the next two years the cost and reliability of these drives is going to equal that of the SATA and SAS drives however for the same money the performance and longevity of the Solid State Drives will make them the only option. Let&#8217;s take a look at the numbers really quick.</p>
<p><strong>How SSD Stacks up</strong></p>
<p>Today for $900 I can buy at my favorite outlet, Fry&#8217;s, Buy.com, NewEgg or wherever (though my butcher is not stocking these yet I am told they will be available in the next few weeks).</p>
<p>240GB Space</p>
<p>0.09ms seek time</p>
<p>Read speed of 800+MB per second</p>
<p>Write speed of 300+MB per second</p>
<p>This is $3.75 per GB which seems like an awful lot and in fact it is and awful lot in terms of storage but let&#8217;s remember that the latest SAS drives which offer similar data throughput but much longer seek times are not even half the price and these Solid State Drives are only 1 year old. The SAS drives are now ending 2 years on the  arket and the price is quite stable. I expect we will see the SSD&#8217;s continue on their path of price decay to somewhere around $.50 per GB or less. At which time the standard platter type Hard Drive will be replaced by the more energy efficient (we haven&#8217;t even talked about this yet) superior performing Solid State Drive. As Benchmark Reviews stated: &#8220;Solid State Drive offers tremendous performance in read and write bandwidth speeds and an exceptional 0.10 ms response time at a attainable price&#8221;.  Anandtech.com has this to say: &#8220;The world&#8217;s fastest consumer desktop hard drive, Western Digital&#8217;s 300GB VelociRaptor can access a random file somewhere on its platters in about 6.83ms; that&#8217;s pretty quick. Most hard drives will take closer to 8 or 9ms in this test. The Intel X25-M however? 0.11ms. The fastest SSDs can find the data you&#8217;re looking for in around 0.1ms. That&#8217;s an order of magnitude faster than the fastest hard drive on the market today.&#8221;</p>
<p><strong>Is SSD for you?</strong></p>
<p>Does this mean that SSD is right for you and your server applications today? For the most part my answer is going to be no. However if you have data that requires very high read times or if you are a performance junky like me then there is no substitute for the latest SSD drives from Intel and OCZ which demonstrate crippling performance numbers that leave even the fastest of conventional drives in the weeds.</p>
<p>Still, early adoption has its hazards and there are some bugs to be worked out with the sequential read/write actions found in a heavily loaded Database Application as well as data buffering where SSD demonstrates weakness that can result in &#8220;stuttering&#8221; or momentary freezes of the Operating System while the Drive recovers from data starvation.</p>
<p>When considering a hard drive choice we now have a new option that requires careful consideration or we risk the possibility of missing out on some very critical performance at a cost increase that may be a worthy burden.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.svwh.net/web-hosting/ssd-fact-or-friction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Virtualization Revolution</title>
		<link>http://blog.svwh.net/web-hosting/the-virtualization-revolution-2/</link>
		<comments>http://blog.svwh.net/web-hosting/the-virtualization-revolution-2/#comments</comments>
		<pubDate>Tue, 05 May 2009 12:38:09 +0000</pubDate>
		<dc:creator>mimi</dc:creator>
				<category><![CDATA[Web Hosting]]></category>

		<guid isPermaLink="false">http://blog.svwh.net/web-hosting/the-virtualization-revolution-2/</guid>
		<description><![CDATA[Web Hosting Services: The Virtualization Revolution
To purchase, install, maintain and secure a state-of-the-art web server is associated with enormous costs. Web hosting pioneers first marketed their “server farms” for companies to simply rent space on remote servers, handling all the security and maintenance needs on behalf of their customers. However, smaller businesses didn’t need all [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Web Hosting Services: The Virtualization Revolution</strong></p>
<p>To purchase, install, maintain and secure a state-of-the-art web server is associated with enormous costs. Web hosting pioneers first marketed their “server farms” for companies to simply rent space on remote servers, handling all the security and maintenance needs on behalf of their customers. However, smaller businesses didn’t need all the bandwidth and computing power available in a single computer, so the ability to rent only the amount they need on a shared server became an attractive proposition.</p>
<p>Ten years ago, hosting services looked to improve the shared services for the rising number of smaller businesses making use of the Internet. Since shared hosting presented too many security risks and bandwidth restrictions to be attractive to serious web developers, they adopted the latest virtualization technology from Linux developers of the Open Source movement. Virtualization systems blurred the line between the dedicated server and shared server by making a single server behave as if it were many individual servers. This way, users could “virtually” have their own private server, along with greater security and bandwidth flexibility.</p>
<p><strong>Virtual Private Servers  (VPS)</strong></p>
<p>Shared hosting service customers access their servers files among other customers, which inherently raises security concerns. The less risky Virtual Private Servers provide private access and file storage, creating the same user experience of a dedicated server, but at significantly less cost. Virtual Private Servers are the ideal solution for web developers, ecommerce sites and other small to medium sized businesses who don’t want a dedicated server, but find shared hosting too restrictive or not powerful enough.</p>
<p>Each VPS runs on its own operating system, and hosting services generally include a selection of applications for online web development and testing, virtual server clustering, etc, and can allow installation of some custom applications. But users are limited to a set amount of disk space, and software restrictions are placed to prevent incompatibility with the virtualized environment. If an application in one VPS crashes, it may impact others residing on the same computer.</p>
<p><strong>The Next Step in Virtualization: <a href="http://www.svwh.net/virtual_dedicated.php">Virtual Dedicated Servers</a>  (VDS)</strong></p>
<p>The VDS is the next step in evolution of the VPS. Like VPS on steroids, it provides users with their own a private IP address, increased security, more consistent bandwidth, more reliability and better crash protection. Because it operates within a fully isolated software environment, other accounts cannot slow down the other VDSs that share the same server with excessive CPU and bandwidth usage.</p>
<p>The VDS behaves more like a dedicated server by dividing one computer into more than 50 private server networks, each running an independent operating system with its own dedicated disk space. Just like a dedicated server, each VDS has an independent operating system, root access, web/mail servers, and unique web IP address. This way, application problems, security flaws and usage in one VDS, can not effect the other VDSs on the shared server computer.</p>
<p><strong>The Future of  Virtualization</strong></p>
<p>As server hardware continues to evolve along with how we  use the Internet,  <em>virtualization</em> technology will undoubtedly continue to find new ways to tap their full potential. We can look forward to more bandwidth and capabilities beyond what we can imagine today, as we live and work in an increasingly virtual world!</p>
<p>By Mimi O’Connor, a contributing author for <a href="http://www.svwh.net/">Silicon Valley Web Hosting</a> and other technology publications</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.svwh.net/web-hosting/the-virtualization-revolution-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
