Building The Independent Wave
Download as ODP, PDF1 like1,299 views
The document discusses the independent wave (Iwave), which refers to implementations of Google Wave that exist outside of Google. It provides an overview of the current status of the Iwave, including several independent server implementations and clients. It also outlines some challenges for further developing the Iwave, such as the need for standardized protocols and the integration of agents. The document advocates for an ecosystem approach to building out the Iwave.
Building The Independent Wave
- 1. Building The Independent Wave
- 2. What is the Independent Wave In a nutshell, the independent wave is all things wavey built outside of Google Wave.
- 3. Status of the Independent Wave
- 4. Where the Independent Wave needs to be
- 5. Why do we need the Independent Wave Every system evolves
- 6. Evolution happens in software as in life, mutations allow old forms to occupy new niches
- 7. Iwave allows for more rapid evolution of Wave through exposure to different environments
- 8. Iwave creates demand for Gwave
- 9. What's happening in the Iwave now Servers FedOne http://code.google.com/p/wave-protocol/ Ruby On Sails http://github.com/danopia/ruby-on-sails Pygowave http://pygowave.net/ Novell Pulse http://www.novell.com/products/pulse/
- 10. Iwave Servers FedOne Googles Open Source Reference Server
- 11. Released under Apache License (opportunity)
- 12. Implements full federation protocol
- 17. Iwave Servers Ruby On Sails Ruby based system
- 19. Achieved federation with wavesandbox.com and FedOne servers
- 20. Character by character transmission
- 21. Last commit was 2 nd December
- 22. Iwave Servers Pygowave Python/Django based system
- 23. Started life as a Gadget testing framework for Gwave
- 24. Still being actively developed
- 25. Actively developing Client/Server Protocol
- 27. Actively developing non Web based client
- 28. Doesn't support federation yet
- 29. Iwave Servers Novell Pulse “Social Web Aggregator”
- 30. Announced Wave support (including Federation)
- 31. Is still awaiting release
- 32. Closed source
- 33. Initially SAAS, then possibly installable product
- 34. What's happening in the Iwave now Clients Qwave http://code.google.com/p/qwaveclient/ Pygowave-qt http://github.com/p2k/pygowave-qt/
- 35. Iwave Clients QwaveClient Cross platform client
- 36. Works with FedOne Iwave server
- 38. QT Based
- 40. Iwave Clients Pygowave-QT Utilises Pygowave Client/Server Protocol
- 41. Proof of concept
- 42. Limited to Pygowave Servers only
- 43. Evolution is driven by challenges Structural Challenges Protocols
- 44. Integration with existing systems
- 45. Agents
- 46. Structural Challenges - Protocols Client / Server Protocol A defined and agreed upon Client/Server protocol is essential to the growth of the Iwave
- 47. Demand for “Native Wave Applications” already exists
- 48. Independent protocols allowed for the development of any number of different email servers and clients
- 49. Open Protocol invites new players into the eco-system
- 50. Structural Challenges - Integration Integration with existing systems Iwave needs to be able to plug in to existing infrastructure
- 51. Integration must happen in as seamless a way as possible
- 52. Iwave needs Agents. No Iwave server that doesn't support Agents will succeed
- 53. For an example of such integration see PlonieBot
- 54. Structural Challenges - Agents Agents offer both challenges and opportunities
- 55. #1 Challenge: How do you prevent malicious Agents from screwing things up? Agents not only hosted locally but remotely
- 56. Determining whether a remote participant is an Agent or not Agents can make or break the Iwave
- 57. Building the Iwave - Foundations Even the most impressive building needs a solid foundation
- 58. Iwave foundation requires Gwave/Google
- 62. Building the Iwave - Standards There is currently one defined Standard Federation Standards give developers certainty
- 63. Developers with certainty tend to be more inclined to develop
- 64. New standards required: Client/Server Protocol
- 65. Agents
- 66. Building the Iwave - Ecologies Remember these: Pygowave
- 67. Ruby on Sails
- 68. FedOne
- 69. Pulse Each of these represents a potential Iwave ecology
- 70. Building the Iwave - Ecologies An Iwave Ecology is made up of the following Server
- 71. Client/s
- 72. Agents
- 73. Users All of which opportunities for developers to become involved in that ecology
- 74. Building the Iwave – Opportunities Many organisations are interested in Wave
- 75. However for many reasons, they can't use Gwave Privacy Legislation
- 77. Infrastructure Requirements Each of these organisations is an opportunity for the Iwave
- 78. Building the Iwave – My Ideal The following is my own Iwave Server Ideal
- 79. This server needs to bridge the divide between Email and Wave: SMTP, POP3, IMAP as native rather than Agent
- 80. Federation
- 81. WCSP (Wave Client-Server Protocol)
- 82. “Groupware”
- 83. WASP (Wave Agent-Server Protocol)
- 84. Building the Iwave – Final Thoughts Gwave and Iwave need each other
- 85. They are part of the greater ecology
- 86. The early work is being done
- 87. People are starting to take the first steps towards the Iwave
- 88. It's exciting, isn't it