COMPATIBILITY

Known compatible issues with Whalin client 2.0.1

• Overview
  • This version includes all the public APIs in Whalin, so that any legacy systems can use this Java client with no re-compilation of the source codes. Due to our test, you can set key/value pairs with whalin client 2.0.1 and get the key/value pairs with this new client for all the native objects and default java object. But some of the APIs are fake, so maybe there are still some compatible issues.
  • Since Whalin only supports memcached text protocol, there is no compatible
    issues when you are using binary or UDP client.
• Known issues
  • The following are fake APIs which are kept in this version to ensure the legacy system can use our Java client:
    • MemCachedClient:
      • setCompressEnable(boolean)
      • setCompressThreshold(long) Compress in LAN is not a good idea, it consumes a lot of CPU resources and achieve little benefit in the size. In our new client, compress is fake APIs, we don’t compress anything in our client, but we will decompress the data from the server side for those key/value pairs set with old whalin client.
    • SockIOPool:
      • getAliveCheck()
      • getFailback()
      • getFailover()
      • getMaintSleep()
      • getMaxBusy()
      • getMaxIdle()
      • setAliveCheck(boolean)
      • setFailback(boolean)
      • setFailover(boolean)
      • setMaintSleep(long)
      • setMaxBusyTime(long)
      • setMaxIdle(long)