Wave Gadget API implementations

2010-12-08 Thread Scott Wilson
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

Re: Wave Gadget API implementations

2010-12-08 Thread Scott Wilson
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 wrote: > >> Hi everyone, >> >>

Re: WebSockets and Socket.io Client Libraries in other languages

2010-12-09 Thread Scott Wilson
On 8 Dec 2010, at 22:30, Sourabh Behra wrote: > I just found out these are some serious security issues with websockets. > mozilla and opera both are not going to use it on upcoming browser versions > untilly trip issue is been fixed I think the turnaround will be pretty quick - its not a fund

Re: WebSockets and Socket.io Client Libraries in other languages

2010-12-09 Thread Scott Wilson
On 8 Dec 2010, at 22:21, Nathanael Abbotts wrote: > Wave in a Box currently uses raw WebSockets or the Socket.io library, based > on the preference of the person running the server. This is all well and > good for web clients, but I struggle to find any implementations of either > of these outside

Re: Committer accounts

2010-12-12 Thread Scott Wilson
Something we've done in Apache Wookie is to have one core server product but a much more open "connector framework" which we encouraged the community to port to C#, Python, Ruby etc. So it may be a strategy to focus on the Wave Protocol server as a single codebase, but identify other areas of t

Re: Integrating Wave server in another project

2011-01-20 Thread Scott Wilson
A lot of projects have also used Apache Wookie - which has Wave Gadget API support - to do this sort of integration of Wave Gadgets into applications. Adding real-time apps to existing platforms such as an enterprise CMS or intranet is a recurring use-case. On 20 Jan 2011, at 03:53, Alex North

Wave on Node

2011-03-16 Thread Scott Wilson
Hi wavers, Just a quick note that I recently updated my Wave Gadget API engine for Node.js and Socket.IO and it now installs nicely using NPM: https://github.com/scottbw/wave-node Enjoy! S

Re: Starting project: Mobile client

2011-04-05 Thread Scott Wilson
On 5 Apr 2011, at 10:11, Yuri Z. wrote: > It think that native clients for IPhone/Android are great ideas and the more > the merrier, however it seems to me that it would be a lot easier to make > Data API based clients first. Or indeed just mobile web applications using JQMobile etc > > Sen

Re: Starting project: Mobile client

2011-04-05 Thread Scott Wilson
On 5 Apr 2011, at 11:34, Zachary “Gamer_Z.” Yaro wrote: > While web clients and data API clients would obviously be easier to write, I > think it would be difficult to get people to adopt the wave protocol and > WIAB unless native clients with full real-time editing are available. Mobile Safari i

Re: Starting project: Mobile client

2011-04-05 Thread Scott Wilson
ould connect to any the user wishes). Not especially. I don't think there is a hard restriction on how many websockets a browser can open. > Also offline caching/sycning > seems ruled out with a web app at least for the moment. Application Cache and LocalStorage should be able to

Re: Starting project: Mobile client

2011-04-05 Thread Scott Wilson
On 5 Apr 2011, at 12:23, Thomas Wrobel wrote: > On 5 April 2011 13:10, Scott Wilson wrote: >> >> On 5 Apr 2011, at 12:02, Thomas Wrobel wrote: >> >>> Its certainly possible to write a native client in android using >>> websockets or socketIO - howe

Re: jWebSocket vs Atmosphere vs Cometd

2011-04-10 Thread Scott Wilson
On 9 Apr 2011, at 22:49, Yuri Z wrote: > By the way, it seems that JWebSocket is licensed under LGPL, is it > compatible with Apache license? Nope. > > 2011/4/10 Nelson Silva > >> Hi all, >> >> I'd really like to be able to create a WAIB WAR deployable in as many >> servers as possible. >> W

Re: Client/Server protocol (again)

2011-07-08 Thread Scott Wilson
On 8 Jul 2011, at 17:27, Joseph Gentle wrote: > Heh - that looks like sharejs: > https://github.com/josephg/ShareJS/ > > I don't have a committee, but I've got OT-based syncronization of > arbitrary JSON objects working. So you can write web apps and keep > complex data structures synced up. >

Re: Client/Server protocol (again)

2011-07-09 Thread Scott Wilson
hat have OT elements, so many that it would seem reasonable to try to standardize some aspects to get greater interoperability across projects. I think this could be one area of work for the W3C FSW group. > On Sat, Jul 9, 2011 at 7:21 PM, ya knygar wrote: >> Scott Wilson, >>

Re: about OT algorithm used in wave

2011-09-20 Thread Scott Wilson
You can also try adapting one of these: https://github.com/scottbw/wave-node https://github.com/josephg/ShareJS The former uses diff-match-patch and JSON structures to merge Wave Gadget states. On 20 Sep 2011, at 07:16, Yuri Z wrote: > If it's not real time, you can try the diff-patch approach

Re: jWebSocket vs Atmosphere vs Cometd

2011-10-14 Thread Scott Wilson
On 14 Oct 2011, at 18:29, Vicente J. Ruiz Jurado wrote: > El 10/04/11 16:32, Nelson Silva escribió: >> Atmosphere (http://atmosphere.dev.java.net >> ) has an Apache License (at least >> that's the one in GitHub) and v0.7 has: >> >> - Native GWT support >> - WebSoc

Re: jWebSocket vs Atmosphere vs Cometd

2011-10-17 Thread Scott Wilson
On 17 Oct 2011, at 06:45, Joseph Gentle wrote: > On Sat, Oct 15, 2011 at 11:14 PM, Vicente J. Ruiz Jurado > wrote: >> El 15/10/11 00:37, Yuri Z escribió: >>> I think someone mentioned that probably just updating to Jetty 7 will >>> suffice. >> >> Sorry, suffice for what? to solve the problem of

Re: jWebSocket vs Atmosphere vs Cometd

2011-10-17 Thread Scott Wilson
On 17 Oct 2011, at 10:18, Vicente J. Ruiz Jurado wrote: > El 17/10/11 09:52, Scott Wilson escribió: >> There's a partial one that only works for Jetty and not Tomcat or other >> servlet containers, but I don't know how actively its being maintained. > > Can you

Re: A Call To Developers

2013-06-13 Thread Scott Wilson
On 12 Jun 2013, at 22:08, Upayavira wrote: > All I can say is, "well said". We need to consider Wave as a young > project - one that really doesn't yet have anything set in stone. > > I've heard Apache described as a 'do-ocracy', that is, he who does, > decides. > > If there's an approach you t