<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div><span style="white-space: pre;"></span>If you want to play with it, I can help you get it up and running.
</div></div></blockquote><div> </div><div>Yups, I would love to take a look at this. Could you point me to any resource to set it up ?<br> <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div><br><div><blockquote type="cite"><div class="gmail_quote"><div>- I really like the fact that the library tries to perform some optimization on storing some native objects. Have you also looked at these optimizations ?
<br> -> Collection of native object<br> -> Class containing native objects </div></div></blockquote><div><br></div></div><div><span style="white-space: pre;"> </span>I'm not sure what you mean by that. Do you mean a single object under a single key, or referencing multiple keys from the server(s)?
<br></div><div><br></div><div><span style="white-space: pre;"> </span>For the former, the default transcoder should be fine. For the latter, it'd be tough because some of the collection can disappear and it'd be spread across multiple servers.
</div></div></div></blockquote><div><br>I think I was not clear in putting my point across. Let me explain with an example<br><br><b>Case 1:</b><br><br> Set<Integer> idSet = new HashSet<Integer>() {{add(1); add(2); add(3) } };
<br> cache.set("test1",idSet); <br><br>In this case the collection's serialized version would be stored ( without any optimization ).<br><br><b>Case 2:</b><br><br>Class A implement Serializable {<br> int a ;
<br> float b ;<br> Date now ;<br>}<br>cache.set("test2",new A()); <br><br>Again the individual members in this class would not be compressed. Atleast in this case I can think of making this class implement Externalizable and perform the compression of the individual class member, if possible.
<br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div><span style="white-space: pre;"></span>1.2.4 is imminent, but isn't a particularly exciting release for me.
</div></div></blockquote><div> </div><div>Hmm.. This is surprising. I was greatly looking forward for features like 64 bit counter, atomic operations, tags :) The feature that I am really waiting for is atomic operations. Currently the memcache code that I have written are not "thread-safe" ( concurrent read and write ). So hoping that java library would start supporting CAS soon.
<br>
</div><br></div>- Rakesh<br>