Tad, Great work on this to date. The ability to use WIAB over Firefox is wonderful. I have also had good luck with Safari as well... on the desktop.
I have not had any luck on Safari (or anything else) on the iPhone, however. Perhaps there is some setting I am missing, or another detail? I pulled the latest code yesterday and have set the socket.io parameter, etc. on the server. Thoughts? Thanks, Mark On Nov 8, 4:35 pm, Tad Glines <[email protected]> wrote: > The Socket.IO stuff should also work for Android and iPhone. The JavaScript > API is very similar to that used by the native WebSockets. Also, Socket.IO > will use WebSockets if it's available. But it added heartbeats so that the > connection doesn't drop due to inactivity. > > I'm also working on a Java client for the socketio-java server. It's needed > because the socketio-java server, even when using WebSockets, uses a special > message format. Jetty 7.2.0 supports the newer draft 3 specification for web > sockets and the special SOcket.IO encoding would not be needed in that case, > but it would require everybody to upgrade to jetty 7.2.0 and I'm not sure > which browsers support that draft version yet. > > -Tad > > On Mon, Nov 8, 2010 at 1:28 PM, James Purser <[email protected]> wrote: > > I think your best bet is to have a look at the Data API. > > > James > > > On Mon, Nov 8, 2010 at 12:50 PM, ThomasWrobel <[email protected]> wrote: > > >> Thanks, but SOCKETIO is a new thing right? As a websocket replacement > >> for (for example) webbrowsers that dont support it. > >> I was more interested in older connection methods (JSON etc) and if > >> they will continue to be support...or even if support has dropped > >> already. > > >> I'm developing for an Android client that use's the WFP, and looking > >> for the most suitable way to manipulate waves on the server. > > >> On Nov 8, 2:20 pm, x00 <[email protected]> wrote: > >> > it is websockets by default, set USE_SOCKETIO to true for wider use. > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Wave Protocol" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]<wave-protocol%[email protected]> > >> . > >> For more options, visit this group at > >>http://groups.google.com/group/wave-protocol?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Wave Protocol" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<wave-protocol%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/wave-protocol?hl=en. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
