I'm writing a Remote caching application and the requirement is that any object can be
stored in the Remote Cache, which is located on another server.
I am using Remoting and have a class that has two functions, GetElement and
SetElement, both of which take Object.
Since any object can be stored in the Remote Cache an object on the client may not
necessarily be on the Server, for e.g. if I call RemoteCache.SetElement("myFoo", foo),
where foo is a class I created, since this class is not on the Server I get a remoting
exception ? Is there any way of getting around this ?
One of my coworkers suggested writing a Client Side sink that serializes to a Byte
stream on a SetElement and then sends that across and does a Deserialize on a
GetElement. I don't like the idea because on a Set, Serialization happens twice, once
by the Remoting infrastructure and once by my own sink, same thing for the Get.
Does anyone have a better idea of doing this ?
Thanks,
John
You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
