Meghansh
July 18th, 2002, 10:32 PM
Hello Frens,
I'm unable to make out some intricacies of Serialization.
An object can be serialized, if it is decorated by [Serializable] attribute. Then what is the need of Binaryformatter. Soapformatter is OK, as it can be required in Web Services.
Secondly, if I send a binary formatted MemoryStream across Appdomain, a proxy of it is passed to it. Any changes in the MemoryStream(and not the object which is constructed by it) should be reflected in the caller AppDomain. But I'm not getting the expected result.
And, if a pass a collection or an array to other AppDomain as a member variable of some MarshalByRefObject inherited object, the changes are not shown in the caller AppDomain.
So I'm a li'le bit confused with the behaviour exhibited by the runtime for Serialization.
Can anybody explain me how CLR does this for us?
Thanx.
I'm unable to make out some intricacies of Serialization.
An object can be serialized, if it is decorated by [Serializable] attribute. Then what is the need of Binaryformatter. Soapformatter is OK, as it can be required in Web Services.
Secondly, if I send a binary formatted MemoryStream across Appdomain, a proxy of it is passed to it. Any changes in the MemoryStream(and not the object which is constructed by it) should be reflected in the caller AppDomain. But I'm not getting the expected result.
And, if a pass a collection or an array to other AppDomain as a member variable of some MarshalByRefObject inherited object, the changes are not shown in the caller AppDomain.
So I'm a li'le bit confused with the behaviour exhibited by the runtime for Serialization.
Can anybody explain me how CLR does this for us?
Thanx.