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 in IOS4 supports websockets[1]...as I think does latest Android - so real-time editing should be possible. (Hmm, maybe I should try doing a wave-node[2] mobile client demo...) > That said, I would love to see _any_ Android client, and I am glad there is > interest in developing one. > > —Zachary “Gamer_Z.” Yaro > On Apr 5, 2011 5:54 AM, "Giacomo Piva" <[email protected]> wrote: >> Ok, You mean porting client API to C language? this is a good starting > point, if someone have some experience and want spend some emails to show me > how to do it I would >> >> Giacomo >> >> Il giorno 05/apr/2011, alle ore 11.05, Chris Mear ha scritto: >> >>> On 4 April 2011 21:56, Giacomo Piva <[email protected]> wrote: >>> >>> <snip> >>> >>>> The main problem with iPhone development is the "closure" to third-part > frameworks and library also (for what I can understand at the moment) the > only way to develop an iPhone native client application is using HTTP > Protocol isn't it? do you think it is possible to develop a client using the > HTTP protocol and not the Python or Java client library? >>> >>> You're right that it'd be difficult (perhaps impossible) to get Python >>> or Java code into an app on the App Store. >>> >>> However, you're not restricted to HTTP networking; you can write C >>> code that reaches right down to the BSD sockets API if you want. >>> >>> Chris >>> >> [1] http://jimbergman.net/websockets-supported-in-ios-4-2/ [2] https://github.com/scottbw/wave-node
