Andrei Pozolotin

got an answer from [Yunhong Gu](http://www.linkedin.com/in/yunhong) re: "udt is pig and allocates 2 native threads for each socket": ``` You can share these sockets on the same port, unless you...

re: "had latency of around 180" - lets agree on common latency ladder for benchmarks? re: "SendRate(Mb/s)" - is it **bytes** or **bits** per second? re: "using a VM running...

re: "true for server sockets too?" answer: ``` accept() socket reuse the same port of the listen() socket. UDT_REUSEADDR applies to rendezvous socket too. ```

1) commit your double-loading test case so I can verify on linux. can annotate `@Ignore` for now, to start via main(). 2) see if basic printf of jdk_clsBoolean hash code...

see p. 103 form http://www.amazon.com/Java-Native-Interface-Programmers-Specification/dp/0201325772 ``` JNIEXPORT jint JNICALL JNI_OnLoad(JavaVM *jvm, void *reserved) { // cls = (*env)->FindClass(env, "C"); // /* Use weak global ref to allow C class to...

it seems we should hide/remove SocketUDT.cleanup() and switch to implicit JNI_OnLoad / JNI_OnUnload instead.

well, that needs be tested.

how about crazy ideas, like: have native library be extracted with time stamp suffix, so they all look different from class loader point of view. then with bit more hacking...

more crazy ideas: say SocketUDT always comes with own class loader. then enforce that you can not get to SocketUDT except via its own class loader.

less crazy idea: take a look on how other popular native libraries like sigar http://support.hyperic.com/display/SIGAR/Home are getting loaded and re-loaded in jboss.