[Mono-devel-list] un-interoperatible classes .NET -> Monoremoting

Anset anset at anset.org
Tue Sep 28 11:00:11 EDT 2004


> I must state that I am not proposing any generic solution here.

That's understood.

> Therefore, by looking at Mono source code (hey, its open source,

Yes it is, but that does not mean it is stable... Things that work now,
could stop working in future, right?
I'm not implying Mono is buggy or something like that. It;s just that, if
remoting isn't part of the standard, anything can and will change, right?

> I would be surprised if you would have to convert string to char arrays
> (I will take a risk: you don't need to!).

Hehe, famous last words? :)

Seriously though, am I right in thinking that this is a serialization issue?
If yes, then I cannot use serialization to save my resources?
But it would mean that remoting using MBR should work?
(Or is there some serialization going on somewhere under the hood?)
If no, then remoting using MBV should work?

I'm pretty sure the answer will be  yes, yes,  no, yes, no, but knowing
beats guessing.

Thank you for your help.


More information about the Mono-devel-list mailing list