<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for duyvu</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#usercomments-e8cbceea" type="application/json"/><link>http://disqus.com/people/duyvu/</link><description></description><language>en</language><lastBuildDate>Thu, 09 Apr 2009 18:28:21 -0000</lastBuildDate><item><title>Re: Google App Engine adds Java support (Review)</title><link>http://www.theodorenguyen-cao.com/2009/04/08/google-app-engine-adds-java-support-review/#comment-8019899</link><description>Sounds like you want to connect to your own database while still using Google App Engine to handle requests and processing.  I don't know the answer to the question.  According to the &lt;a href="http://code.google.com/appengine/docs/java/jrewhitelist.html" rel="nofollow"&gt;JRE whitelist&lt;/a&gt;, the relevant classes necessary to connect to DataSource are available. However, &lt;a href="http://code.google.com/appengine/docs/java/urlfetch/" rel="nofollow"&gt;the docs&lt;/a&gt; also allude to the fact that Google App Engine apps are only allowed to connect to other resources over HTTP and HTTPS which I read to mean I can't connect to another data source.  &lt;a href="http://couchdb.apache.org/" rel="nofollow"&gt;CouchDB&lt;/a&gt; is a document database with a REST API which sounds like you could possibly use. &lt;br&gt;&lt;br&gt;Google has incentive to keep all of your data on their servers by claiming power in the cloud and bind/support your development through GAE.&lt;br&gt;&lt;br&gt;Given all of this, there's nothing stopping you from writing your own export/backup mechanism.  You could created a crond job that iterates over all of the objects in your datastore and generate a big SQL file that you could use to import to MySQL.  It would development require some work but might be worthwhile if you are concerned that you may want to move off of GAE in the future.&lt;br&gt;&lt;br&gt;That said, give it a shot! And let me know what you find out :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Thu, 09 Apr 2009 18:28:21 -0000</pubDate></item><item><title>Re: Setup Apache on Mac OSX Leopard</title><link>http://www.theodorenguyen-cao.com/2009/01/28/setup-apache-on-mac-osx-leopard/#comment-5618221</link><description>I was working with raw HTML and javascript just by itself. Not in a rails or java app.   When working off the filesystem, local file references don't 404 in firebug and there are some other oddities that seem to happen. For example, code that keys off of http or https doesn't work because the protocol is file://</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Wed, 28 Jan 2009 11:18:52 -0000</pubDate></item><item><title>Re: Cleaning up iPhoto</title><link>http://www.theodorenguyen-cao.com/2009/01/25/cleaning-up-iphoto/#comment-5612329</link><description>Thanks Pete, I actually am trying out Aperture out right now. It imported all of my photos from iPhoto nicely.  It takes forever to generate the thumbnails/previews it needs.  My iPhoto Library is only 24 gigs and Aperture's library is 9 gigs after importing the photos.  I assume that means there's 9 gigs worth of thumbnails and previews it generated. I really like the simple layout for event browser. The showslide feature is a little slow to start.  I'll have to try it out over the course of the next couple weeks and see how it goes.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Wed, 28 Jan 2009 01:56:38 -0000</pubDate></item><item><title>Re: Introducing theoandpat.com</title><link>http://www.theodorenguyen-cao.com/2009/01/11/introducing-theoandpatcom/#comment-5252638</link><description>haha no problem man. you better get to it. :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Sat, 17 Jan 2009 20:30:13 -0000</pubDate></item><item><title>Re: gem update fails - can&amp;#8217;t find header files for ruby</title><link>http://www.theodorenguyen-cao.com/2008/09/03/gem-update-fails-cant-find-header-files-for-ruby/#comment-2379396</link><description>lol :(</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Tue, 16 Sep 2008 04:01:19 -0000</pubDate></item><item><title>Re: Discuss with disqus</title><link>http://www.theodorenguyen-cao.com/2008/06/16/discuss-with-disqus/#comment-2096164</link><description>Hey, Hooman. I think it's an interesting service.  But for the average blogger (me) with the same 5 or 6 people that follow their blog, the realized gain from Disqus is minimal.  The value of Disqus for a blogger is to bring more people into conversations started from their blog. Sure, if you blog about an original topic that is controversial, you might find utility in Disqus.  Otherwise, the commenting system that comes with any blog software will suit you just fine.  This single-sign-on discussion system is a turn off for many people.  One of the most powerful motivators of internet discussions is the anonymity of the user.   You mean I can say what I want and don't have to be held accountable? In that case, I'll be honest!  &lt;br&gt;&lt;br&gt;As a discussion participant, it's nice to be able to track your comments across all the sites you visit.  But for me, most of those sites are not using Disqus so I personally haven't realized that benefit.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Wed, 03 Sep 2008 21:49:47 -0000</pubDate></item><item><title>Re: Discuss with disqus</title><link>http://blog.notedpath.com/2008/06/16/discuss-with-disqus/#comment-687617</link><description>Yeah, the whole idea of an open commenting system that enables more of a multi-way communication is really what I was looking for.  I like the idea of threaded conversations that was one of the reason gmail became so popular.  With something like Disqus, all roads don't have to lead to your blog in order for the rest of the interwebs to join in discussions. Your blog can simply be a pit stop.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Mon, 16 Jun 2008 19:16:28 -0000</pubDate></item><item><title>Re: Discuss with disqus</title><link>http://blog.notedpath.com/2008/06/16/discuss-with-disqus/#comment-687602</link><description>Yeah, the whole idea of an open commenting system that enables more of a multi-way communication is really what I was looking for.  I like the idea of threaded conversations that was one of the reason gmail became so popular.  With something like Disqus, all roads don't have to lead to your blog in order for the rest of the interwebs to join in discussions. Your blog can simply be a pit stop.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Mon, 16 Jun 2008 19:14:19 -0000</pubDate></item><item><title>Re: Stickies to Quickies</title><link>http://blog.notedpath.com/2008/05/02/stickies-to-quickies/#comment-680066</link><description>Test comment on Disqus.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">duyvu</dc:creator><pubDate>Sun, 15 Jun 2008 14:43:30 -0000</pubDate></item></channel></rss>