<?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"
	>
<channel>
	<title>Comments on: Subdomains + Development  =&#160;Sucks</title>
	<atom:link href="http://particletree.com/notebook/subdomains-development-sucks/feed/" rel="self" type="application/rss+xml" />
	<link>http://particletree.com/notebook/subdomains-development-sucks/</link>
	<description>Everyone needs a hug.</description>
	<pubDate>Wed, 19 Nov 2008 11:33:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Andy</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21764</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 11 Jul 2007 03:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21764</guid>
		<description>&lt;p&gt;I think everyone has come to a great conclusion, but what is the best method for creating 'folders' ala
www.mysite.com/username.  I assume this would be done by adding a rule to the apache rewrite engine?  Or is it an actual folder? Thoughts?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think everyone has come to a great conclusion, but what is the best method for creating &#8216;folders&#8217; ala
<a href="http://www.mysite.com/username" rel="nofollow">http://www.mysite.com/username</a>.  I assume this would be done by adding a rule to the apache rewrite engine?  Or is it an actual folder? Thoughts?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21523</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Fri, 29 Jun 2007 17:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21523</guid>
		<description>&lt;p&gt;Those are two very good points. Why make more work for yourself and require more money for SSL certificates when using a folder name will work just as well? Save yourself a headache and heed this sage advice.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Those are two very good points. Why make more work for yourself and require more money for SSL certificates when using a folder name will work just as well? Save yourself a headache and heed this sage advice.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Organ</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21363</link>
		<dc:creator>Derek Organ</dc:creator>
		<pubDate>Thu, 14 Jun 2007 02:58:32 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21363</guid>
		<description>&lt;p&gt;yea i see your points and we made the same choice a good while ago at http://1timetracking.com.   We have pretty big databases for each user and each domain is for a company so i think it makes more sense.  I think the subdomain idea gives the end user more ownership of what they have purchased or subscribed to.&lt;/p&gt;

&lt;p&gt;I do think in your situation it probable wasn't needed.   I think like with basecamp if the users have other external users coming to the app then there is value in it.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>yea i see your points and we made the same choice a good while ago at <a href="http://1timetracking.com" rel="nofollow">http://1timetracking.com</a>.   We have pretty big databases for each user and each domain is for a company so i think it makes more sense.  I think the subdomain idea gives the end user more ownership of what they have purchased or subscribed to.</p>

<p>I do think in your situation it probable wasn&#8217;t needed.   I think like with basecamp if the users have other external users coming to the app then there is value in it.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Bialasinski</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21144</link>
		<dc:creator>Martin Bialasinski</dc:creator>
		<pubDate>Sat, 02 Jun 2007 13:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21144</guid>
		<description>&lt;p&gt;Agreed about the phishing problem. http://wufoo.com/forms/auth/welcome/ is no better than http://auth.wufoo.com/forms/welcome/&lt;/p&gt;

&lt;p&gt;You don't need to use the NetInfo Manager. You can instruct it to use /etc/hosts. Just put this into /etc/lookupd/hosts:&lt;/p&gt;

&lt;p&gt;LookupOrder Cache FF NI DNS DS&lt;/p&gt;

&lt;p&gt;(FF mean flat file = /etc/hosts)&lt;/p&gt;

&lt;p&gt;You might have to kill -HUP the lookupd.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Agreed about the phishing problem. <a href="http://wufoo.com/forms/auth/welcome/" rel="nofollow">http://wufoo.com/forms/auth/welcome/</a> is no better than <a href="http://auth.wufoo.com/forms/welcome/" rel="nofollow">http://auth.wufoo.com/forms/welcome/</a></p>

<p>You don&#8217;t need to use the NetInfo Manager. You can instruct it to use /etc/hosts. Just put this into /etc/lookupd/hosts:</p>

<p>LookupOrder Cache FF NI DNS DS</p>

<p>(FF mean flat file = /etc/hosts)</p>

<p>You might have to kill -HUP the lookupd.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Harry</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21128</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Thu, 31 May 2007 16:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21128</guid>
		<description>&lt;p&gt;I can see your point when it comes to ssl. One domain is easier and cheaper.
I can see the point about phishing, but this will always be so if you allow a user to insert a form into a page. Any page.&lt;/p&gt;

&lt;p&gt;I wouldn't, however, say developing with subdomains is a problem. I have used/tested them on both mac and windows test servers without problem. My only pain was adding the subdomains to the host/NetInfo Manager one at a time. Not a problem for testing as you will never have to do more than 20 or so.
Subdomains are easy for end users to remember, make them feel special and make the general url structure shorter and easier to pass between friends.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I can see your point when it comes to ssl. One domain is easier and cheaper.
I can see the point about phishing, but this will always be so if you allow a user to insert a form into a page. Any page.</p>

<p>I wouldn&#8217;t, however, say developing with subdomains is a problem. I have used/tested them on both mac and windows test servers without problem. My only pain was adding the subdomains to the host/NetInfo Manager one at a time. Not a problem for testing as you will never have to do more than 20 or so.
Subdomains are easy for end users to remember, make them feel special and make the general url structure shorter and easier to pass between friends.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21127</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Thu, 31 May 2007 13:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21127</guid>
		<description>&lt;p&gt;As for the phishing example in #24: Now is http://wufoo.com/forms/auth/welcome/ (the folder variation) any better than http://auth.wufoo.com/forms/welcome/ (the sub-domain variation)?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>As for the phishing example in #24: Now is <a href="http://wufoo.com/forms/auth/welcome/" rel="nofollow">http://wufoo.com/forms/auth/welcome/</a> (the folder variation) any better than <a href="http://auth.wufoo.com/forms/welcome/" rel="nofollow">http://auth.wufoo.com/forms/welcome/</a> (the sub-domain variation)?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: PohEe.com</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21087</link>
		<dc:creator>PohEe.com</dc:creator>
		<pubDate>Tue, 29 May 2007 02:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21087</guid>
		<description>&lt;p&gt;By using subdomain, it save u some money from purchase new domain.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>By using subdomain, it save u some money from purchase new domain.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: PJ Hyett</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21083</link>
		<dc:creator>PJ Hyett</dc:creator>
		<pubDate>Mon, 28 May 2007 00:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21083</guid>
		<description>&lt;p&gt;I know you guys are a PHP shop, but in Rails we've done stuff like this in the past:&lt;/p&gt;

&lt;pre&gt;
# config/routes.rb
if RAILS_ENV == 'development'
  map.connect '/mobile', :controller =&#62; { :mobile }
else
  map.connect '', :controller =&#62; { :mobile }, :subdomain =&#62; { 'm' }
end
&lt;/pre&gt;

&lt;p&gt;So, in production http://m.chow.com works, but for development you go to http://localhost:3000/mobile so you don't need to bother with /etc/hosts.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I know you guys are a PHP shop, but in Rails we&#8217;ve done stuff like this in the past:</p>

<pre>
# config/routes.rb
if RAILS_ENV == 'development'
  map.connect '/mobile', :controller =&gt; { :mobile }
else
  map.connect '', :controller =&gt; { :mobile }, :subdomain =&gt; { 'm' }
end
</pre>

<p>So, in production <a href="http://m.chow.com" rel="nofollow">http://m.chow.com</a> works, but for development you go to <a href="http://localhost:3000/mobile" rel="nofollow">http://localhost:3000/mobile</a> so you don&#8217;t need to bother with /etc/hosts.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Hirsch</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21080</link>
		<dc:creator>Ben Hirsch</dc:creator>
		<pubDate>Sun, 27 May 2007 17:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21080</guid>
		<description>&lt;p&gt;I agree that this adds many extra degrees of difficulty for development but you end up sacrificing a strength of the app. Having personalized sub-domains may be &lt;em&gt;worth&lt;/em&gt; the cause of the pain. I can understand not using them for social network / community type sites, though. In some cases I think I might think twice before signing up for a web service that I knew I would be using quite often and would not have the ability to go to or send a client directly to myDomain.theAppDomain.com. To me, the customer, I believe I would think twice if I knew I might get the subdomain with the competitor's service. I guess it depends on what's being offered.&lt;/p&gt;

&lt;p&gt;Alternatively, I think it could be smart to give people the subdomain, but just for redirection purposes. So, they could use this: myDomain.theAppDomain.com but it would route (redirect) them to: http://theAppDomain.com/myDomain/ to sign in.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I agree that this adds many extra degrees of difficulty for development but you end up sacrificing a strength of the app. Having personalized sub-domains may be <em>worth</em> the cause of the pain. I can understand not using them for social network / community type sites, though. In some cases I think I might think twice before signing up for a web service that I knew I would be using quite often and would not have the ability to go to or send a client directly to myDomain.theAppDomain.com. To me, the customer, I believe I would think twice if I knew I might get the subdomain with the competitor&#8217;s service. I guess it depends on what&#8217;s being offered.</p>

<p>Alternatively, I think it could be smart to give people the subdomain, but just for redirection purposes. So, they could use this: myDomain.theAppDomain.com but it would route (redirect) them to: <a href="http://theAppDomain.com/myDomain/" rel="nofollow">http://theAppDomain.com/myDomain/</a> to sign in.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: xc</title>
		<link>http://particletree.com/notebook/subdomains-development-sucks/#comment-21077</link>
		<dc:creator>xc</dc:creator>
		<pubDate>Sun, 27 May 2007 10:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/subdomains-development-sucks/#comment-21077</guid>
		<description>&lt;p&gt;Everyone needs a hug.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Everyone needs a hug.</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.262 seconds -->
