<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><channel rdf:about="https://www.bibsonomy.org/user/draganigajic/appengine"><title>BibSonomy bookmarks for /user/draganigajic/appengine</title><link>https://www.bibsonomy.org/user/draganigajic/appengine</link><description>BibSonomy RSS Feed for /user/draganigajic/appengine</description><items><rdf:Seq><rdf:li rdf:resource="http://ajaxian.com/archives/what-does-google-app-engine-mean-for-ajax-developers"/><rdf:li rdf:resource="http://www.datacenterknowledge.com/archives/2008/Apr/08/video_google_app_engine.html"/><rdf:li rdf:resource="http://aralbalkan.com/1307"/><rdf:li rdf:resource="http://www.42topics.com/dumps/appengine/doc.html"/><rdf:li rdf:resource="http://bret.appspot.com/entry/experimenting-google-app-engine"/><rdf:li rdf:resource="http://groovie.org/articles/2008/04/13/google-datastore-and-the-shift-from-a-rdbms"/><rdf:li rdf:resource="http://www.webmonkey.com/tutorial/Get_Started_With_Django"/><rdf:li rdf:resource="http://idlewords.com/2008/08/using_google_app_engine_with_amazon_web_services.htm"/><rdf:li rdf:resource="http://appengine-cookbook.appspot.com/"/><rdf:li rdf:resource="http://www.niallkennedy.com/blog/2008/11/twitter-front-end-rewrite.html"/><rdf:li rdf:resource="http://24ways.org/2008/using-google-app-engine-as-your-own-cdn"/><rdf:li rdf:resource="http://code.google.com/p/google-mobwrite/"/></rdf:Seq></items></channel><item rdf:about="http://ajaxian.com/archives/what-does-google-app-engine-mean-for-ajax-developers"><title>Ajaxian » What does Google App Engine mean for Ajax developers?</title><description></description><link>http://ajaxian.com/archives/what-does-google-app-engine-mean-for-ajax-developers</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:43+02:00</dc:date><dc:subject>ajax ajaxian appengine google </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2011-07-13T18:13:43+02:00&#034; href=&#034;http://ajaxian.com/archives/what-does-google-app-engine-mean-for-ajax-developers&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://ajaxian.com/archives/what-does-google-app-engine-mean-for-ajax-developers&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ajax"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ajaxian"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/google"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.datacenterknowledge.com/archives/2008/Apr/08/video_google_app_engine.html"><title>Video: Google App Engine - Data Center Knowledge</title><description></description><link>http://www.datacenterknowledge.com/archives/2008/Apr/08/video_google_app_engine.html</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:43+02:00</dc:date><dc:subject>appengine google video </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2011-07-13T18:13:43+02:00&#034; href=&#034;http://www.datacenterknowledge.com/archives/2008/Apr/08/video_google_app_engine.html&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://www.datacenterknowledge.com/archives/2008/Apr/08/video_google_app_engine.html&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/google"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/video"/></rdf:Bag></taxo:topics></item><item rdf:about="http://aralbalkan.com/1307"><title>Building Flash applications with Google App Engine at Aral Balkan</title><description>Aral on Flash, SWX, Flex, ActionScript, and life.</description><link>http://aralbalkan.com/1307</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:42+02:00</dc:date><dc:subject>amf appengine blogpost flash </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Aral on Flash, SWX, Flex, ActionScript, and life.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/amf"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/blogpost"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/flash"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.42topics.com/dumps/appengine/doc.html"><title>Using Django with Google Appengine</title><description></description><link>http://www.42topics.com/dumps/appengine/doc.html</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:42+02:00</dc:date><dc:subject>appengine django </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2011-07-13T18:13:42+02:00&#034; href=&#034;http://www.42topics.com/dumps/appengine/doc.html&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://www.42topics.com/dumps/appengine/doc.html&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/django"/></rdf:Bag></taxo:topics></item><item rdf:about="http://bret.appspot.com/entry/experimenting-google-app-engine"><title>Experimenting with Google App Engine - Bret Taylor&#039;s blog</title><description></description><link>http://bret.appspot.com/entry/experimenting-google-app-engine</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:42+02:00</dc:date><dc:subject>100+ appengine blogpost google </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2011-07-13T18:13:42+02:00&#034; href=&#034;http://bret.appspot.com/entry/experimenting-google-app-engine&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://bret.appspot.com/entry/experimenting-google-app-engine&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/100+"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/blogpost"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/google"/></rdf:Bag></taxo:topics></item><item rdf:about="http://groovie.org/articles/2008/04/13/google-datastore-and-the-shift-from-a-rdbms"><title>Google Datastore and the shift from a RDBMS</title><description></description><link>http://groovie.org/articles/2008/04/13/google-datastore-and-the-shift-from-a-rdbms</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:42+02:00</dc:date><dc:subject>100+ appengine blogpost google </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2011-07-13T18:13:42+02:00&#034; href=&#034;http://groovie.org/articles/2008/04/13/google-datastore-and-the-shift-from-a-rdbms&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://groovie.org/articles/2008/04/13/google-datastore-and-the-shift-from-a-rdbms&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/100+"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/blogpost"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/google"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.webmonkey.com/tutorial/Get_Started_With_Django"><title>Get Started With Django - Webmonkey</title><description></description><link>http://www.webmonkey.com/tutorial/Get_Started_With_Django</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:14+02:00</dc:date><dc:subject>100+ appengine django framework howto python tutorial web2.0 webFramework webapp webdev </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2011-07-13T18:13:14+02:00&#034; href=&#034;http://www.webmonkey.com/tutorial/Get_Started_With_Django&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://www.webmonkey.com/tutorial/Get_Started_With_Django&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/100+"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/django"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/framework"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/howto"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/python"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/tutorial"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/web2.0"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/webFramework"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/webapp"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/webdev"/></rdf:Bag></taxo:topics></item><item rdf:about="http://idlewords.com/2008/08/using_google_app_engine_with_amazon_web_services.htm"><title>Using Google App Engine With Amazon Web Services</title><description></description><link>http://idlewords.com/2008/08/using_google_app_engine_with_amazon_web_services.htm</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:08+02:00</dc:date><dc:subject>amazon appengine aws cloudComputing ec2 google python </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2011-07-13T18:13:08+02:00&#034; href=&#034;http://idlewords.com/2008/08/using_google_app_engine_with_amazon_web_services.htm&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://idlewords.com/2008/08/using_google_app_engine_with_amazon_web_services.htm&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/amazon"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/aws"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/cloudComputing"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ec2"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/google"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/python"/></rdf:Bag></taxo:topics></item><item rdf:about="http://appengine-cookbook.appspot.com/"><title>Google App Engine Cookbook</title><description></description><link>http://appengine-cookbook.appspot.com/</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:13:04+02:00</dc:date><dc:subject>100+ appengine from:realsplog </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2011-07-13T18:13:04+02:00&#034; href=&#034;http://appengine-cookbook.appspot.com/&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://appengine-cookbook.appspot.com/&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/100+"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/from:realsplog"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.niallkennedy.com/blog/2008/11/twitter-front-end-rewrite.html"><title>Rewriting Twitter for web best practices</title><description>Last week I decided to rewrite the Twitter.com front-end on Google App Engine to incorporate modern front-end programming best practices, exceptional performance, and establish a solid platform for further development. TwitterFE.com is a fully-functional read-only clone of Twitter.com designed to make your web browser sing. I created the site as an example of web development best practices anyone can integrate into their web presence.  The new web front-end on TwitterFE.com features localized templates, expressive markup, distinct URL structures, integrated site search, geo-distributed dynamic and static servers, and more available features than Twitter.com. In this post I will outline some of the changes I&#039;ve applied to the Twitter front-end reproduction as they apply to general front-end web development.</description><link>http://www.niallkennedy.com/blog/2008/11/twitter-front-end-rewrite.html</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:12:22+02:00</dc:date><dc:subject>appengine twitter usability webdesign webdev </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Last week I decided to rewrite the Twitter.com front-end on Google App Engine to incorporate modern front-end programming best practices, exceptional performance, and establish a solid platform for further development. TwitterFE.com is a fully-functional read-only clone of Twitter.com designed to make your web browser sing. I created the site as an example of web development best practices anyone can integrate into their web presence.  The new web front-end on TwitterFE.com features localized templates, expressive markup, distinct URL structures, integrated site search, geo-distributed dynamic and static servers, and more available features than Twitter.com. In this post I will outline some of the changes I&amp;#039;ve applied to the Twitter front-end reproduction as they apply to general front-end web development.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/twitter"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/usability"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/webdesign"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/webdev"/></rdf:Bag></taxo:topics></item><item rdf:about="http://24ways.org/2008/using-google-app-engine-as-your-own-cdn"><title>24 ways: Using Google App Engine as Your Own Content Delivery Network</title><description>A content delivery network, or CDN, is a system of servers spread around the world, serving files from the nearest physical location. Instead of waiting for a file to find its way from a server farm in Silicon Valley 8,000 kilometres away, I can receive it from London, Dublin, or Paris, cutting down the time I wait. The big names — Google, Yahoo, Amazon, et al — use CDNs for their sites, but they’ve always been far too expensive for us mere mortals. Until now. There’s a service out there ready for you to use as your very own CDN. You have the company’s blessing, you won’t need to write a line of code, and — best of all — it’s free. The name? Google App Engine. In this article you’ll find out how to set up a CDN on Google App Engine. You’ll get the development software running on your own computer, tell App Engine what files to serve, upload them to a web site, and give everyone round the world access to them.</description><link>http://24ways.org/2008/using-google-app-engine-as-your-own-cdn</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:12:18+02:00</dc:date><dc:subject>100+ appengine blogpost cdn django google hosting infrastructure network performance python tutorial webdev </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;A content delivery network, or CDN, is a system of servers spread around the world, serving files from the nearest physical location. Instead of waiting for a file to find its way from a server farm in Silicon Valley 8,000 kilometres away, I can receive it from London, Dublin, or Paris, cutting down the time I wait. The big names — Google, Yahoo, Amazon, et al — use CDNs for their sites, but they’ve always been far too expensive for us mere mortals. Until now. There’s a service out there ready for you to use as your very own CDN. You have the company’s blessing, you won’t need to write a line of code, and — best of all — it’s free. The name? Google App Engine. In this article you’ll find out how to set up a CDN on Google App Engine. You’ll get the development software running on your own computer, tell App Engine what files to serve, upload them to a web site, and give everyone round the world access to them.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/100+"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/blogpost"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/cdn"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/django"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/google"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/hosting"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/infrastructure"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/network"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/performance"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/python"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/tutorial"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/webdev"/></rdf:Bag></taxo:topics></item><item rdf:about="http://code.google.com/p/google-mobwrite/"><title>google-mobwrite - Google Code</title><description>MobWrite converts forms and web applications into collaborative environments. Create a simple single-user system, add one line of JavaScript, and instantly get a collaborative system. Demos  Each of these demos is globally collaborative, meaning everyone is sharing the same space. With luck there will be someone else using these demos with whom you can play. If not, open the demos in two different windows and collaborate with yourself.  Editor  A simple collaborative plain-text editor. MobWrite is extremely good at resolving collisions which other systems would fail on. Form  This form demonstrates collaboration with all the standard HTML form elements. Note that the onchange event is called remotely when the checkbox is ticked, thus allowing forms to react normally to changes. Spreadsheet  This 50-cell spreadsheet is an abuse of MobWrite (there are more efficient ways of synchronizing grids of data). But it shows what can be done.</description><link>http://code.google.com/p/google-mobwrite/</link><dc:creator>draganigajic</dc:creator><dc:date>2011-07-13T18:12:11+02:00</dc:date><dc:subject>ajax appengine code collaboration editor googlecode javascript python software sync </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;MobWrite converts forms and web applications into collaborative environments. Create a simple single-user system, add one line of JavaScript, and instantly get a collaborative system. Demos  Each of these demos is globally collaborative, meaning everyone is sharing the same space. With luck there will be someone else using these demos with whom you can play. If not, open the demos in two different windows and collaborate with yourself.  Editor  A simple collaborative plain-text editor. MobWrite is extremely good at resolving collisions which other systems would fail on. Form  This form demonstrates collaboration with all the standard HTML form elements. Note that the onchange event is called remotely when the checkbox is ticked, thus allowing forms to react normally to changes. Spreadsheet  This 50-cell spreadsheet is an abuse of MobWrite (there are more efficient ways of synchronizing grids of data). But it shows what can be done.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ajax"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/appengine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/code"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/collaboration"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/editor"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/googlecode"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/javascript"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/python"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/software"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/sync"/></rdf:Bag></taxo:topics></item></rdf:RDF>