cfmemcached v1.2 released today - download yours now
I tested and uploaded a new release for cfmemcached today. This update includes a new java library from each branch. Greg and Dustin updated their code, so i'm passing it along to you for your caching pleasure.
This new release includes a number of upgrades to the coldfusion piece as well.
cfmemcachedNew -
- included the updated java library from dustin that has some performance fixes
- Update coldfusion library to have a configurable timeout. Base timeout can be set as well as a time out per request, in case you want to extend it to wait for a long running cache or a bulk operation that needs to wait on several memcached responses
- more cftries and catches - trying to make the application fail gracefully
cfmemcachedOld -
- included the updated java library from greg that has some performance fixes
- added a lot more cftries and catches to make it fail better, ie fail gracefully so that it doesn't impact your overall application.
as always, cfmemcached is located at cfmemcached.riaforge.org -- Coldfusion memcached
first of all thank for your great work on this. We are using memcached
1.1 here with about 2m cache hits / day and it works great.
While trying out the 1.2 i come across this strange behavior.
When i run the memcachedtest and i leave the value for simpleval at
simpleval43466665532 it will not set this value and the set2.get() does return a NO.
For all following variables (set3, set4 etc.) the setX.get() will also return a NO
even though they are being set.
Now the strangest thing. If i cut 2 numbers at the end to make it
simpleval434666655
it will work just fine.
Can you please have a look into this. The queries and arrays are also setting fine, just this one value.
I used the Hermes Vmware Appliance but that is too old :(
Installed a fresh 1.2.5 memcached and now it works fine.
setDefaultTimeoutUnit();
setDefaultRequestTimeout();
instead of :
variables.defaultTimeoutUnit = setDefaultTimeoutUnit();
variables.defaultRequestTimeout = setDefaultRequestTimeout();
as using the assignment will always set true, true than the actual values for both timeOuts