FW: [Mono-devel-list] un-interoperatible classes .NET ->Monoremot ing

[Paul Stevens]

True as far as serialization goes custom serialization should solve the
problem, as for remoting between the two frameworks Mono -> .NET or .NET ->
Mono, the best option would probably be to implement some kind of remoting
broker that can transform the serialized stream into the correct object for
its relevant framework... 

-----Original Message-----
From: Anset [mailto:anset at anset.org] 
Sent: 29 September 2004 09:33 AM
To: Lluis Sanchez
Cc: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-devel-list] un-interoperatible classes .NET
->Monoremoting

Hi Lluis,

Thank you for your answers.

If I may ask one further clarification:

> > If yes, then I cannot use serialization to save my resources?
>
> You can. If you care about interoperability, just make sure you don't
> serialize any class that is not under your control.

This would mean that my classes can only use primitive types, right?
If I use say a sortedlist, I might break the interoperability?

Now if this is "only" a serialization problem, I could of course just
implement the (de)serialization methods myself and not use the standard
classes... There I could (de)serialise everything myself. Or do I miss
something?

The whole serialization & remoting idea is pretty new to me, so sorry to be
asking such basic questions.

Thank you for your time,

Anset

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

**************************************************************************************************************************
Everything in this e-mail and attachments relating to the official business of MultiChoice Africa is proprietary to 
the company. Any view or opinion expressed in this message may be the view of the individual and should not automatically 
be ascribed to the company.  If you are not the intended recipient, you may not peruse, use, disseminate, distribute or 
copy this message. If you have received this message in error, please notify the sender immediately by email, facsimile 
or telephone and destroy the original message.
**************************************************************************************************************************