Re: Wave documentation

2011-07-09 Thread Soren Lassen
Google copied the Wave API documentation to waveprotocol.org last year: https://sites.google.com/a/waveprotocol.org/wave-protocol/wave-apis It's all there and belongs to Apache Wave now. (There are some broken links in the waveprotocol.org copy but that should be easy to fix.) With regard to you

Re: Client/Server protocol (again)

2011-07-09 Thread ya knygar
>As indeed is Apache :-) without a doubt! >I think there is a lot of potential in FSW; the hard part as always being >identity and privacy. certainly, i hope, eventually FreedomBox team with all the mighty Debian hackers would solve all the issues, i like that - their nonconformism combined with

Re: Client/Server protocol (again)

2011-07-09 Thread Thomas Wrobel
oh, quick question; wheres the current wiab repository? ~~ Reviews of anything, by anyone; www.rateoholic.co.uk Please try out my new site and give feedback :) On 9 July 2011 23:11, Thomas Wrobel wrote: > Guess I could have a go at those - they seem client based stuff so I > should be able

Re: Client/Server protocol (again)

2011-07-09 Thread Scott Wilson
On 9 Jul 2011, at 20:24, ya knygar wrote: > excuse me, it's https://apps.mozillalabs.COM/ > anyway - their recent work looks like from a great non-profit organization :) As indeed is Apache :-) Certainly there are a lot of real-time services and specifications around at the moment that have OT

Re: Client/Server protocol (again)

2011-07-09 Thread Thomas Wrobel
Guess I could have a go at those - they seem client based stuff so I should be able to handle it. I'll download a new checkout now and have a look. However, Can I have confirmation of the state of that proposed c/s protocol however as Joseph didn't know? At he moment Im a guy that doesn't know ho

Re: Client/Server protocol (again)

2011-07-09 Thread ya knygar
excuse me, it's https://apps.mozillalabs.COM/ anyway - their recent work looks like from a great non-profit organization :) On Sat, Jul 9, 2011 at 7:21 PM, ya knygar wrote: > Scott Wilson, > your > https://github.com/scottbw/wave-node > work and experience, W3C or WHATWG web apps working group wo

Re: Client/Server protocol (again)

2011-07-09 Thread ya knygar
Scott Wilson, your https://github.com/scottbw/wave-node work and experience, W3C or WHATWG web apps working group work, and your contribution to XCCC could really Help us all on developing a suitable for most format for web-apps in Gadget's point-of-view, in POW, since PyGoWave we had a number of v

Re: Client/Server protocol (again)

2011-07-09 Thread Yuri Z
A great way to familiarize yourself with WIAB is by comepleting StarterProject . 2011/7/9 Joseph Gentle > On Sat, Jul 9, 2011 at 8:19 AM, Thomas Wrobel wrote: > >> As far as I know, the clie

Re: Client/Server protocol (again)

2011-07-09 Thread Joseph Gentle
On Sat, Jul 9, 2011 at 8:19 AM, Thomas Wrobel wrote: >> As far as I know, the client-server protocol for wave in a box is >> pretty stable at this point. Its documented here: >> http://www.waveprotocol.org/protocol/design-proposals/clientserver-protocol >> ... Though that documentation is probably

Re: Client/Server protocol (again)

2011-07-09 Thread ya knygar
>I have to point out, none of these solutions are actually federated - >and thus unsuitable for anyone wishing to make a open network where >anyone can run a server. WFP and WIAB was the highest! priority for pyofwave.info, we could say - the PyOfWave was the only besides WIAB which were aimed for