Question

在标题中很难描述这一点。

I m 想通过一个可变体:不是一种实例,不是收集构成物体的财产,而是实际变量:handle至物体。

The reason for this is that I am dealing with resources that can be located on the filesystem, on the network, or in-memory. I want to create URI handler that can handle each of these in a consistent manner, so I can have schemes like eg.

file://
http://
ftp://
inmemory://

你们有这个想法。这是我试图指出的最后一个例子:是否在某种程度上可以表明在Ruby提到物体的情况,然后利用这种说法来制定新的参考? 我确实有兴趣对参引<>,而不是object表示兴趣。理想的情况是,采用<条码>目标#object_id等,这种编号很容易获得,并用它来在其他地方产生一个新变量,提及同一目标。我知道,这确实可能很脆弱,因此是一种不寻常的使用案例:只要现有变数使物体不再被收集的垃圾,它就只能在一个鲁比拉进程内开展工作,但两者都是在<代码>inmemory上。计划一米发展。

The only alternatives I can think of are:

marshal the whole object and cram it into the URI, but that won t work because the data in the object is an image buffer - very large
Create a global or singleton purgatory area to store a variable for retrieval later using e.g. a hash of object_id:variable pairs. This is a bit smelly, but would work.

任何其他想法,StackOverflowers?

Answer 1

The s Object Space._id2ref:

f = Foo.new #=> #<Foo:0x10036c9b8> 
f.object_id #=> 2149278940 
ObjectSpace._id2ref(2149278940) #=> #<Foo:0x10036c9b8>

除停车场收集点外,<代码> 物体空间对jruby(大体如此,以致于因违约而残疾)处以重刑。

Answer 2

易变器是鲁比拉的 objects。你们不仅不能与他们结婚,而且可以与他们一道工作。你只能做一些与物体有关的事情,这些变量为t。

(really) ice objects

Answer 3

可查阅MagLev ,这是在以下网址上建立的一个替代的“Rub”执行项目:Gemstone 。它有一个分发物体模型,可能适合你的使用。

Objects are saved in the central Gemstne instance (with some nifty caching) and can be accessed by any number of remote worker instances. That way, any of the workers act on the same object space and can access the very same objects simultaneously. That way, you can even do things like having the global Garbage Collector running on a single Ruby instance or seamlessly moving execution at any point to different nodes (while preserving all the stack frames) using Continuations.

友情链接