the Android client is right now a little bit behind the WAMP
implementation of Python (client and server) and JS.
WAMP is still evolving .. we've added some small features .. I guess
what it breaks is the initial WAMP welcome
message that contains a unique random session ID, which is used for
- exclude individual clients from receivers when publishing
- (optionally) for client authentication purposes
I'll fix it shortly (tomorrow or day after ..)
I report here when its ready again .. sorry.
Tobias
https://github.com/oberstet/AutobahnAndroid/issues/2
https://github.com/oberstet/AutobahnAndroid/issues/3
I have tested it using
Android 2.3.3
AutobahnAndroid _current_
Autobahn _current_
It should work with Android >= 2.2 and also the latest Autobahn release
(0.4.10).
==
If you have Android 4.x devices (or other versions), I'd be glad to hear
if that works also.
==
Please note: I did not update the AutobahnAndroid JAR (yet) .. its
somewhat annoying / error prone
to do manually. You need to use the source.
Should you - by chance - know how to automate that, I'd be happy to hear!
https://github.com/oberstet/AutobahnAndroid/issues/4
==
Should you run into problems, feel free to ask .. AutobahnAndroid is
still beta (unlike AB Py, which is
quite mature) .. issues will arise.
/Tobias
I now included startup code like
http://android-sdk.appspot.com/reference/android/os/StrictMode.html
and I can see the violation even on 2.3
D/StrictMode(11924): at
de.tavendo.autobahn.WebSocketConnection.connect(WebSocketConnection.java:194)
It's like I suspected .. the initial socket connect is the source of
evil (the background readers/writers thereafter
are no problem and work as expected).
Thus:
We need to do the initial socket connect already on a short-lived
background thread.
This is a high-prio problem ..
https://github.com/oberstet/AutobahnAndroid/issues/6
and I will fix it very soon .. however I need a 3+/4 device first;)
So lets say next week ..
\Tobias