Wave Hackathon Intro
Download as ppt, pdf2 likes901 views
This document discusses Google Wave and its potential for building real-time web applications. Some key points: - Waves use XML and operational transformation to enable collaborative editing in real-time. - The Wave protocol is open source and decentralized, allowing users to run their own Wave servers. - Extensions called "robots" can be built to add functionality like games, polls and more. - Challenges include establishing etiquette for managing long conversations and avoiding spam. But the technology provides opportunities for building new types of collaborative apps and reasoning over real-time data on the entire web.
![Jose Quesada, [email_address] , http://josequesada.name Twitter: @quesada Reasoning with the entire web: http://larkc.eu](https://image.slidesharecdn.com/wavehackathonintro-091114051910-phpapp01/85/Wave-Hackathon-Intro-2-320.jpg)
Wave Hackathon Intro
- 1. Wave hackathon intro Jose Quesada, Max Planck Institute, Berlin RuPy 2009, Posnan, Poland
- 2. Jose Quesada, [email_address] , http://josequesada.name Twitter: @quesada Reasoning with the entire web: http://larkc.eu
- 3. 油
- 5. Each wave is an XML document. It can be rendered as html Uses html 5 XMPP Operational Transformation (OT). It defines a set of油operations, transformations, and the documents they can be applied to
- 6. HTTP vs XMPP REST A mapping of CRUD operations on a RDBMS to: GET POST PUT DELETE Web frameworks isolate us from seeing http at work
- 7. Credit: Andres Ferrate, getting started with google Wave. O reilly
- 8. HTTP vs XMPP
- 9. HTTP vs XMPP Decentralization Presence Presence data overhead Real time possible. But this is not as big deal as it seems. http://jasonkolb.com/weblog/2009/09/why-google-wave-is-the-coolest-thing-since-sliced-bread.html
- 10. WE
- 11. ARE
- 12. DOING
- 13. IT
- 14. If we are doing web apps over HTTP, we are doing them wrong WRONG
- 15. The wave protocol is free and open source. You can run your own wave server Alternatives (other real-time frameworks) Tornado: extracted from friendfeed Twister Diesel
- 16. COMPONENTS
- 17. 油
- 18. Robots - gadgets Robots are like participants
- 19. Credit: Andres Ferrate, getting started with google Wave. O reilly
- 20. Waves are embeddable In an application (example: desktop wave client) Web page (example: substitute blog post and comments)
- 21. Sandbox vs standard wave Standard ~ 100.000 users You normally get invites Quite a lot of activity Sandbox: lucky few - not that many people to test your extensions, but you can go to the standard wave for that
- 22. INSPIRATION
- 23. 油
- 24. 油
- 25. http://sites.google.com/site/gwaveextensions/extensions-list Chatbots Conversion Games Groups Integration Language Polling Search / Aggregation Utilities Wave Management
- 28. RESOURCES
- 29. 油
- 30. A Wave in itself: Wave Programming tutorials!油 https://wave.google.com/wave/?pli=1#restored:wave:googlewave.com!w%252BW779r_dkQ Google Wave http://www.slideshare.net/monika7/google-wave-2063865 Google Wave http://www.slideshare.net/jrigerl/google-wave Advanced Wave Presentation http://www.slideshare.net/bedney/wave-presentation-1933385 Making dodgy robots with Google Wave http://www.slideshare.net/guest3eb9a3c/making-dodgy-robots-with-google-wave Google Wave Robot API - Marcel Prasetya http://docs.google.com/present/view?id=ajfcq4h4mvxw_0f9xph2cg 油
- 31. Wave extension In 5 steps http://jeez.eu/2009/10/11/creating-a-google-wave-extension-in-5-steps/ Reddit : Wave: http://www.reddit.com/r/wave App engine: http://www.reddit.com/r/AppEngine/ For gadgets, step-by-step guide (in php!) http://jeez.eu/2009/10/11/creating-a-google-wave-extension-in-5-steps/
- 32. Wave Extension Design Principles Make It Wave-y Make It Easy to Use Make It Easy to Install Make It Look Good Make It Useful Or Fun! (http://code.google.com/apis/wave/extensions/designprinciples.html)
- 33. Gotchas: Robot Wars Problem: Because you can invite more than one robot into a wave, you can inadvertently end up building a new version of Robot Wars. For example, one robot could reply to another one's changes and vice versa. Solution : give robots limited quota, so infinite loops will ultimately run out of steam.
- 34. SOCIAL ASPECT
- 35. Some A-list bloggers didnt like it Scoble: Google Wave crashes on beach of overhype Google Waves unproductive email metaphors But, early adopters/geeks are not the audience.
- 36. User experience improvements will make great extensions Pain points You need to read through a lot of crap It's hard to manage a long wave 油 Spam: Nobody can enter if they are not invited
- 37. Like twitter, it sits in an uncomfortable position
- 38. wavetiquette proper wave etiquette is still forming When is it ok to delete posts? Should you edit your own response or respond to your response? Starting new waves versus resurrecting old ones (and how to politely point people to older waves)
- 39. Hack away 2.5 hrs. Pair up Lets move to a place where we can walk around, see what others are doing, get back to coding Come up with an idea. See blog post at rupy for step-by-step things to do Theres a wave already started. Search for rupy If you have no wave account, match up with someone who does
- 40. END
- 41. Scale to the entire web Do reasoning with open word assumption Retrieval in real-time Go beyond logics Use cases: Real time city Cancer monographs for WHO Gene expression finding
- 42. To follow: @enkido working on wave robot IDE, scipy http://gist.github.com/raw/150983/8b27179d9defbf5a1ac25e574c9e51ec2f981998/gistfile1.txt Tips from a hackathon attendant
- 43. 油
Editor's Notes
- #9: Opera tried to build a server on everyones browser
- #10: IRC: robots are possible, but primitive. This is better. You have a much more powerful client It saves bandwidth Better for privacy
- #15: Its not because its real-time. Its because its a different paradigm
- #26: Theres a catalog, so before you start coding your idea, make sure is not invented already