First of all. I really do not appreciate to have my email publically exposed like that (I am already spamed enaugh). So please edit your answer to delete it.
In what concerns socket.io inside the BrowserComponent, I finally got it working with no issue, even inside the Simulator (websockets works just fine in it). That is why I deleted my post (the 'connection timeout' message I had on my server was actually unrelated to socket.io). As for porting the android socket.io library to codenameone, this is clearly not something I would call 'straight forward'. It could have been if cn1 supported the complete java API but, as not the case, a port to cn1 would requiere many changes into the java socket.io lib and its dependencies. And socket.io do not only relly on websockets, it also use some AJAX or JSONP protocol for the handshake. So I am still considering whether it is worth the hastle porting the java socket.io lib to cn1 or make a cn1 native wrapper around this android lib and the socket.io swift lib for iOS rather than just stick with using the javascript version into the BrowserComponent... -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/7bb70fa5-3459-47f2-a029-95ace13340b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
