I have created cache (basically a Dictionary(tkey, tvalue)) that is remoted via TCP. It allows me to load up the cache with 1+gb of data that remains cache between calls and client startups. Multiple callers can call on the remoted cache and retrieve data. I'd like to avoid the binary serialization cost on the "server" side by storing a pre-serialized version of the object in the cache and build a remoting transport that doesn't have to do serialization while responding to a request. Here's the ideal situation The data in the cache is binary serialized to disk, the cache starts up and reads the serialized data into memory, pulls out the key and stores the serialized data as the value and the key in the Dictionary. A caller configures itself to call the cache via RemotingConfiguration.configure then makes a call on the cache. The data is looked up in the cache and the raw value is sent back to the caller. On the server there is no serialization cost. On the client, the value retrieved must be deserialized (this can't be avoided). Any pointers would be greatly appreciated. -- ==================== eAndy ====================
