On 5 April 2011 13:10, Scott Wilson <[email protected]> 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? >> 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. >> 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?
