search

Atmosphere / wasync

WebSockets with fallback transports client library for Node.js, Android and Java
http://async-io.org
161 stars 47 forks source link

Strange behaviour on android #100

Closed wollodev closed 9 years ago

wollodev commented 10 years ago

I've still problems with android on wasync. I use wasync in an AsyncTask to avoid the NetworkOnMainThreadException (or use your approach in the android chat example). Several problems occours. I work with an atmosphere-spring backend and wasync, atmosphere-js (newest versions) and use only websockets.

In my application a message is sent from the backend directly to the client after opening the connection. This message is ignored with wasync. Additionally, the second message which is explicit sent by me ignores the trackMessageSize, because the wasync thinks it is the first message at all (atmosphere protocol, ignore the trackmessagesize of the first message). After deactivating the protocol option the right message is received.

The whole program as JavaApp works without problems.

jfarcand commented 10 years ago

Please use the mailing list for question ... if you can send a test case that would be great. Thanks

flowersinthesand commented 10 years ago

@wollodev Is there any update on this? I'm interested in difference in HTTP I/O between in JVM and Dalvik.