[Ironruby-core] IronRuby's Marshal.dump doesn't work with CLR types, or ruby types backed by a CLR type
lists at ruby-forum.com
Mon Jul 9 22:37:57 UTC 2012
Thanks for the useful feedback. In the interim, I am maintaining the
object on the DRb server-side and keeping interaction with the object
basic enough to maintain fairly easily. A rudimentary proxy, if you
will. Long term, though, I will follow-up on your starting points and
endeavor to get both marshaling and serializing working. I haven't
run-across the object id issue that you mentioned with DRb, however I
believe this is by nature of the work around.
I'll keep you in the loop as it progresses, it's something that will
probably get put on the shelf for a week or two as I deal with more
straight-forward tasks first.
Orion Edwards wrote in post #1067985:
> I personally haven't done any work on it since those last emails. I'm
> away from work for the next week or so, so I can't go and look it up
>>From my vague memories of the code, it shouldn't be much work to get
> it marshalling .NET objects that use the .NET Serialization API's. I
> had it working, I just needed to write extra code for .NET fundamental
> types like Int64 which aren't handled.
> Nonserializable .NET objects are much harder however (maybe
> I too was trying to get DRB to work, but the big issue with that is
> that DRB uses ruby object id's to keep track of different objects on
> both sides of the connection. CRuby has a special format for object
> id's, and critically, you should never get duplicate object id's.
> IronRuby's implementation of Object ID's on the other hand is very
> basic, and it's quite easy to get duplicate object id's, (completely
> ruining DRb). I'd start with that :-)
> Certainly, if you get DRb working, I'd be a grateful user of it :-)
Posted via http://www.ruby-forum.com/.
More information about the Ironruby-core