On 8 Dec 2010, at 21:15, Alex North wrote: > That looks pretty cool.
Thanks! > Wave in a Box uses the underlying wave model and transport to propagate > changes, since it's already there, but that's definitely not the only good > way. Because Wave already has this infrastructure I'm not sure how useful > your code is to the project right now. But it's fantastic to have more hosts > for the real-time gadgets that Wave enables, so thanks for volunteering. I sort of assumed the initial code donation had a pretty complete implementation :-) I'm just thinking that other projects support multiple implementations (e.g. Shindig in Java and PHP flvaours) or themed sub-projects (e.g. Lucene has the Solr, Lucy & Droids sub-projects) so it may be worth thinking about whether the Apache Wave community will focus on a single implementation, or coordinate a collection of implementations using different technologies but common specifications. (For example, if its the latter it may be worth also reaching out to the PygoWave team.) > > On 9 December 2010 00:17, Scott Wilson <[email protected]>wrote: > >> Hi everyone, >> >> I've worked on several Wave Gadget API implementations and was wondering >> how these might relate to the Apache Wave incubator project? >> >> A Comet-based implementation in Java using DWR has been developed in Apache >> Wookie(incubating). However, recently we've been discussing recently in the >> Wookie community whether we want to retire this implementation at some point >> in the future and adopt or develop another using a different base >> technology. >> >> So I developed another implementation that uses Node.js, WebSockets and >> Redis - this is currently on Github (under ASL2.0 license): >> >> https://github.com/scottbw/wave-node >> >> I'd certainly be happy to donate this code if we think its appropriate to >> develop it further within the Apache Wave project. >> >> S
smime.p7s
Description: S/MIME cryptographic signature
