Not sure to tell you the truth, my android foo is pretty limited. However you might want to put the question to the Android mailing list and see what the answer is.
Another option is Socket.IO though by the looks of it, it isn't well supported. James On Mon, Nov 8, 2010 at 4:51 PM, Davide Carnovale < [email protected]> wrote: > yes James, i think the cause is likely to be the introduction of websockets > as the main way to talk to the server as they're more heavy computationally > wise. do you know if sixfire websocket implementation (the one used by WiaB) > can be run on android? any other hint that could help me getting to a > solution? > > thanks again > > Davide > > 2010/11/9 James Purser <[email protected]> > >> Davide could it be something to do with the move to WebSocket/SocketIO? >> >> James >> >> On Mon, Nov 8, 2010 at 4:04 PM, Davide Carnovale < >> [email protected]> wrote: >> >>> In order to develop a proof of concept client i started by building a >>> small >>> API out of the wave-protocol source tree (i'm using WiaB code from hg >>> repository taken 2010/11/08). I've added the following to build.xml: >>> <target name="dist-android-client" depends="stage" >>> description="Assembles the FedOne Android client lib"> >>> <jar destfile="${jar.outfile-android-client}"> >>> <fileset dir="${staging}"> >>> <include name="com/google/common/**/*" /> >>> <include name="org/waveprotocol/**/*" /> >>> <include name="com/google/protobuf/**/*" /> >>> <include name="org/apache/commons/codec/**/*" /> >>> <include name="com/sixfire/websocket/*" /> >>> <include name="com/google/gson/**/*" /> >>> <include name="com/dyuproject/protostuff/**/*" /> >>> <include name="org/codehaus/jackson/**/*" /> >>> <include name="javax/inject/**/*" /> >>> <include name="jline/**/*" /> >>> <include name="com/google/inject/**/*" /> >>> </fileset> >>> </jar> >>> </target> >>> >>> and i've created a new android project in eclipse, which contains a >>> single class that implements WaveletOperationlistener. >>> >>> When compiling the app in eclipse i get a lot of >>> "warning: Ignoring InnerClasses attribute for an anonymous inner class >>> that doesn't come with >>> an associated EnclosingMethod attribute. (This class was probably >>> produced by a broken compiler.)" >>> errors. >>> This seems not to be a problem as from various searches on the web. >>> But when i try to run the application the phone reboots. No messages >>> on eclipse debugger. no clues at all. >>> Investigating on the InnerClasses errors resulted in a problem related >>> to the dalvik vm >>> not able to convert code not generated by java 1.5 >>> Taking out the API external jars one at a time has shown that the >>> problematic >>> jars are JLine and google inject. So i downloaded the source of JLine >>> and recompiled it for 1.5. Warning gone. >>> But google inject is still there with the warning. >>> phone reboots. >>> If i leave out the google inject dependency the client "works", >>> meaning it doesn't crash and reboot, >>> but gives a timeout exception while connecting the socket. ( naturally >>> i have a server running and chrome is able to connect to it) >>> So now i'm stuck there. >>> >>> Should i change wave-protocol code to allow a longer timeout? >>> Did anyone managed to get this to work on android? >>> any advice or docs i should read? >>> >>> as a side note, the 0.2 version of the wave-protocol used to work and >>> i'm able to connect, get waves >>> and add/remove blips. >>> >>> thanks in advance >>> >>> Davide >>> >>> -- >>> 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]<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.
