Comments on: The URL Shortener as a Cloud Database http://softwareas.com/the-url-shortener-as-a-cloud-database Mahemoff's Podcast/Blog - Web, Programming, Usability from the Author of 'Ajax Design Patterns' (AjaxPatterns.org) Wed, 17 Mar 2010 14:29:59 -0400 http://wordpress.org/?v=2.8.3 hourly 1 By: Chris http://softwareas.com/the-url-shortener-as-a-cloud-database/comment-page-1#comment-433038 Chris Thu, 21 May 2009 09:25:59 +0000 http://softwareas.com/?p=534#comment-433038 <p>If you have a 2000 character maximum URL, it gives you 48 extra characters for the database row, which will then fit nicely into memory</p> If you have a 2000 character maximum URL, it gives you 48 extra characters for the database row, which will then fit nicely into memory

]]> By: mahemoff http://softwareas.com/the-url-shortener-as-a-cloud-database/comment-page-1#comment-432924 mahemoff Wed, 20 May 2009 13:07:16 +0000 http://softwareas.com/?p=534#comment-432924 <p>Fred, true - I think that <em>is</em> semantics! I would say the data is indeed being stored in the cloud, in the url shorteners, instead of being held in user's browsers as bookmarks, in emails, and in post-it notes (in the form of a long URL with all state info).</p> Fred, true – I think that is semantics! I would say the data is indeed being stored in the cloud, in the url shorteners, instead of being held in user’s browsers as bookmarks, in emails, and in post-it notes (in the form of a long URL with all state info).

]]> By: FND http://softwareas.com/the-url-shortener-as-a-cloud-database/comment-page-1#comment-432888 FND Wed, 20 May 2009 08:14:02 +0000 http://softwareas.com/?p=534#comment-432888 <p>Interesting concept, Mike! However - I apologize in advance for arguing semantics - in your scenario (the one not violating ToS), you're not really storing state in the cloud, are you? It's your app's original URI which captures the actual data - URL shorteners just provide an alias there.</p> Interesting concept, Mike!
However – I apologize in advance for arguing semantics – in your scenario (the one not violating ToS), you’re not really storing state in the cloud, are you? It’s your app’s original URI which captures the actual data – URL shorteners just provide an alias there.

]]>