> Perhaps a compromise would be augment the API, or your wrapper, such > that it provides a Future<byte[]> which has more well-known semantics > to clients. >
Already there :) I'll publish the source once my second pass is done and I believe I've removed all the rope. Kevin -- Founder/CEO Spinn3r.com Location: San Francisco, CA AIM/YIM: sfburtonator Skype: burtonator Work: http://spinn3r.com
