Sessions at Open Source Bridge 2009 about Web Applications

Wednesday 17th June 2009

• Deploying to the Edge from CouchDB

  by J Chris Anderson

  Apache CouchDB makes the perfect vehicle for extremely distributed applications. CouchDB can serve HTML and other static web assets, while providing dynamic access to data. CouchDB's validation functions and rendering capablities mean you can write your web app in pure JavaScript. Once it's done it can spread through ad-hoc sharing. When users have full access to the source code, interesting things happen. The application models are different. I'll run you though some of the major differences. Learning how to program extremely distributed case will make you stronger at building more traditional scalable web services.

  • CouchDB
  • Deployment
  • Web Applications

  At 10:00am to 10:45am, Wednesday 17th June

  Coverage note

• Agile JavaScript Testing

  by Scott Becker

  h3. Intro
  * Test Driven Development - What is it, why do it, what are the advantages?
  * Challenges of web applications - browser quirks, asynchronous ajax, dynamic-ness of JavaScript language
  * Future VMs will run JS faster, making "bigger", more processing intensive apps possible within a browser
  * Traditionally web applications have most business logic running server side.
  * Testing for server-side web applications has matured over the past few years
  * AJAX applications have large amounts of code executing in the browser in JavaScript
  * This creates a growing need for testing at the browser level, but this area is still young and not as widely practiced

  h3. What do we gain?
  * Stable development - iterate without fear of breaking existing features
  * Easier refactoring - rewrite the guts of your app and be confident it continues to work
  * Speed - stop refreshing and clicking through your app to verify things are working, thats what computers are for
  * Automation - repeatable tests help you do the right thing every time, without having to think about it

  h3. Getting Started
  * What libraries and methodologies exist for JavaScript testing?
  * A simple example - a client-side form validation library and a suite of tests for verifying it works as expected

  h3. Going further
  * A complex example - integration testing, scripting user stories
  * Testing across multiple browsers
  * Incorporating JS tests into a larger development workflow with server-side tests
  * Continous integration - running tests automatically, every time you commit

  • Agile
  • JavaScript
  • Testing
  • Web
  • Web Applications

  At 11:20am to 12:05pm, Wednesday 17th June

  Coverage note

Thursday 18th June 2009

• Your Shell History In The Cloud

  by josh cronemeyer

  A presentation about Shellsink: a simple, open source hack that stores your shell history in Google's big table. The presentation will cover Shellsink usage, the App Engine implementation, as well as using Launchpad's personal package archives for distribution via apt-get.

  Shellsink Feature Set:
  * Permanent and unlimited storage of shell history
  * Pull commands back out of the sink and into your shell based on a tag or keyword
  * Searchable shell history
  * Tagable shell history
  * Annotateable shell history
  * Aggregate shell history from multiple computers into one grand unified history
  * RSS feed of your shell history that you can filter

  • Google App Engine
  • Launchpad
  • Unix
  • Web Applications

  At 5:00pm to 5:45pm, Thursday 18th June

  Coverage note