Thanks! That’s actually very helpful. I’ll start dissecting the JNI code. While I would love to be able to debug this stuff, I have a feeling this might be a quicker approach and probably something I’d have to do anyway.
/Morten ________________________________ From: Nash, George <[email protected]> Sent: Tuesday, October 31, 2017 2:27:51 PM To: Macieira, Thiago Cc: Morten Nielsen; [email protected] Subject: RE: [dev] Android and C-SDK Yes there are some implementation details that call the Android API. Without digging into the code I can't recall off the top of my head which portions of the code do use Android specific calls. All of the code that has Android specific details is isolated in the java/iotivity-android folder. -----Original Message----- From: Macieira, Thiago Sent: Tuesday, October 31, 2017 2:23 PM To: Nash, George <[email protected]> Cc: Morten Nielsen <[email protected]>; [email protected] Subject: Re: [dev] Android and C-SDK On terça-feira, 31 de outubro de 2017 14:21:43 PDT Nash, George wrote: > The Android port (i.e. Java implementation on android) uses the C++ > SDK in the JNI code. Since C++ uses the C SDK it ultimately works out > that the C SDK is being used on Android. I think there are certain implementation details that go back via JNI to call to Android API. Isn't the network monitor doing that? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
