Hi Julian, Then we should update the RawSocketChannel as that is based on OIO ... the PCAP Channel I don't really care as it's for testing and development only anyway.
Chris Am 07.01.20, 12:46 schrieb "Julian Feinauer" <[email protected]>: Hi Chris, I agree that we should never use Oio for Productive Code (instead of Serial where its fine, I think). But, yes, we could add other transports for "edge" cases or something. Currently that’s just a toy project we try to get running, but I see some interesting options there : ) Julian Am 07.01.20, 12:39 schrieb "Christofer Dutz" <[email protected]>: Hi all, I Think the OIO options are usually marked as deprecated in favor of NIO. But I think we could do one thing. The same way I can pass in a different ChannelFactory for testing or PCAP input or whatever we want to use, we could have additional TCP channel-factories that explicitly use OIO. Then we could add a parameter such as "androidCompatability=true" to the string and use that instead? Would that be an option? Chris Am 07.01.20, 12:01 schrieb "Julian Feinauer" <[email protected]>: Hi folks, yesterday our good friend @Niklas Merz<mailto:[email protected]> did a little bit of Android Vodoo to make an Example of PLC4X for Android here: https://github.com/NiklasMerz/plc4x-android-demo So does PLC4X work on Android? No, not really… It turns out, that Netty does not really work on Android (well it does but not with our settings)… So we could see how far we’d like to push that. As it seems one way could be to use Oio Instead of Nio (https://stackoverflow.com/questions/11007879/client-server-application-for-android-with-netty-integration). Currently I see no need for that, but I think its an interesting Idea (not talking about if someone should really do it, but COULD do it). If I find some time I will create a branch which builds Netty on Oio instead of Nio and test it further with Niklas. Best Julian
