> It's been discussed, but not a lot of effort has gone into coming > up > with storage compatibility. > > It's pretty easy in my client to write a transcoder object to meet > your exact requirements (basically assert the value to be a string, > get the UTF-8 bytes from it and set the flags to whatever you want), > but I wouldn't consider that a general long-term solution. >
My problem appears to be that I can't get the data out with your client (I assume yours is the Spy 'Optomised' Java client) as it 'sees' the flag telling it the data is compressed, and attempts to de-compress (the un-compressed) data immediately so I get a null back [this what I've interpreted from setting up an ErrorHandler] Are you saying there might be a way for me to disable to automatic de-compression (enableCompression(false) only seems to affect compression [makes sense I guess!) so I can get this data out ? Thanks - Ciaran
