[Mono-list] remoting mono with MS' CLR?
Thong (Tum) Nguyen
Tue, 8 Jul 2003 15:20:36 +1200
I can understand the need to interop with MS.NET, but I don't think
sterilization compatibility is an easy goal. It's no easy task to
replicate internal, implementation specific details from MS.NET. If MS
upgrade ArrayList then interop between MS.NET versions will be broken as
The solution is to use the same collections package on both runtimes
and/or use a more customized serialization format (e.g. XML).
PS. Java has the same problems with serialization.
> -----Original Message-----
> From: email@example.com [mailto:mono-list-
> firstname.lastname@example.org] On Behalf Of Miguel de Icaza
> Sent: Monday, 7 July 2003 5:21 a.m.
> To: Thong (Tum) Nguyen
> Cc: email@example.com; firstname.lastname@example.org
> Subject: RE: [Mono-list] remoting mono with MS' CLR?
> > Serializing the collection classes would require the collection
> > to be an exact clone of the Microsoft classes. Not only do the
> > names have to match exactly, but the underlying implementation
> > (how/when/where those fields are used) has to match exactly too.
> Good point Thong.
> In a few cases, we might be able to change the implementation to match
> the Microsoft runtime behavior, to maximize interop. It is not
> but at least worth trying.
> Mono-list maillist - Monoemail@example.com