So that one needs another server to access the wiab server right? LocalClient>>AppEngineServer>>WiaB Server right?
Or am I misunderstanding the description? On 7 April 2011 18:11, Yuri Z <vega...@gmail.com> wrote: > Well, there are a few mobile friendly clients for Wave - > micro-wave.appspot.com being the most popular. I made some modifications to > micro-wave in order to adapt it to WIAB and called it micro-box, you can > find the source code at https://github.com/vega113/microbox. > > 2011/4/7 Giacomo Piva <p...@innovativa.it> > >> Il giorno 05/apr/2011, alle ore 14.37, Thomas Wrobel ha scritto: >> >> > Offtopic indeed :) >> > >> > Its more an issue of what Giacomo wants to do though. >> >> Yes... :) >> So... finally, none is working at the development of an iPhone client, so, >> does someone have some idea on which is the best way? >> Using HTTP Protocol Data API is the best way or what? >> >> If someone is interested too, please contact me, thank you. >> >> > I know my application wouldn't be possible on a web app for awhile, >> > but maybe Giacomos would. >> > >> > I'll look into Obigo/WARP/W3C widget solutions anyway though as I dont >> > know much about them. >> > I'm not sure Id want any special server requirements though - would be >> > nice if all clients could work with all wiab servers. >> > >> > Cheero, >> > Thomas >> > >> > >> > On 5 April 2011 13:43, Scott Wilson <scott.bradley.wil...@gmail.com> >> wrote: >> >> >> >> On 5 Apr 2011, at 12:23, Thomas Wrobel wrote: >> >> >> >>> On 5 April 2011 13:10, Scott Wilson <scott.bradley.wil...@gmail.com> >> 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 - however the tricky bit is what your sending >> >>>>> via them and processing the response's. >> >>>>> >> >>>>> My own application demands a native client, as I'm dealing with 3d >> and >> >>>>> camera manipulation, >> >>>> >> >>>> Well, however long it takes until W3C HTML Media Capture support makes >> it into more webkit builds... >> >>>> >> >>> >> >>> And proformance of image processing and 3d catchs up with native ones. >> >>> It willl happen, but I think we are talking 5 years rather then 6 >> >>> months here. Is WebGL on any mobile browser yet? >> >> >> >> Its in webkit, but not in mobile browsers yet AFAIK - seems pretty close >> to ready though given some recent demos on Android using Fennec. >> >> >> >>> >> >>>>> however wouldn't even a simple mobile web-based >> >>>>> client be limited to one server? (compared to a native client which >> >>>>> could 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. >> >>>> >> >>> >> >>> I was thinking more SOP issures, not to mention privacy problems. Your >> >>> going via one domain to manipulate data on another. I guess its like >> >>> how gmail can access hotmail - certainly doable but Id rather just >> >>> have a native IMAP client and connect directly. >> >> >> >> For SOP you can use a broker as a workaround. Alternatively you can >> deploy it as a W3C Widget and use the WARP access manifest with a wildcard. >> (However that currently means deploying using Opera or Obigo). >> >> >> >> Or you can use CORS on the servers. >> >> >> >>> >> >>>>> Also offline caching/sycning >> >>>>> seems ruled out with a web app at least for the moment. >> >>>> >> >>>> Application Cache and LocalStorage should be able to manage it. >> >>> >> >>> Not sure how this currently bahaves on mobile browsers. >> >>> I think if it was easy/efficiant google wouldn't have a native gmail >> >>> app with android phones no? >> >> >> >> I think we're starting to stray off the main topic into one of those >> native-vs-web arguments :-) >> >> >> >> Lets just say - a Wave mobile web application is possible, but would >> currently involve a few compromises as browser implementations and device >> hardware catches up with the specs. >> >> >> >> Personally I'd start with a limited mobile web app and add advanced >> capabilities later as they became available through the mobile browser. But >> thats a personal view; I think you're wanting to do something a little >> different to that - all the best! >> > >> >> >
