(public).sospep.subjects ~ view article ~ why-real-estate-is-attractive

<h1 style="text-align: center;">real estate -&nbsp;</h1>
<h2>[WHAT]</h2>
<ol>
<li><a href="http://blog.ezliu.com/why-real-estate-tech-is-so-attractive-for-founders/" target="_blank">http://blog.ezliu.com/why-real-estate-tech-is-so-attractive-for-founders/</a>&nbsp;- Eric Lui runs a startup named <a href="http://rocketlease.com" target="_blank">Rocket Lease</a> that facilitates the process of the 'rental application' between landlord and tenant. landlords can use his service to take rental application 'online/electronically' versus tenants having to fill out paper based forms(still prevelant/dominant) in the industry. Landlords can than order ] credit reports ] eviction reports ] criminal thru his service.&nbsp;</li>
<li><a href="http://blog.ezliu.com/2013-stats/" target="_blank">http://blog.ezliu.com/2013-stats/</a>&nbsp;- Eric documents the growth of his startup&nbsp;</li>
<li><a href="http://blog.ezliu.com/" target="_blank">http://blog.ezliu.com/</a>&nbsp;-&nbsp;</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>[comments][real-estate]&nbsp;Second comment. On the pegged webserver that's preventing me from reading the article: First, really, just loadtest your webserver. It's not hard, try apache bench ("ab") as a starting point. Second, shut off unnecessary parts when they're being slow (like analytics), a database access for comments, etc. Load them asynchronously from JS (putting the CPU load on the client), and let the page render when you get back an error or timeout. Unless the primary content on the page is dynamic, the page should get to the client without any I/O except for the NIC.</li>
<li>]</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li>]</li>
</ol>
<h2>[WHEN]</h2>
<ol>
<li>]</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>]</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>]</li>
</ol>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] ch-002-ideas FROM [ Book] startup-guide IN [ libraries] business