I am searching for the application/server that allows to store
objects and easy manipulate them. It must support caching,
transactions and loading by request, so if I loaded some object and
want to access some subobject it must be automaticly loaded from DB.
In other way if I create on clientside some object that attached to
stored object, then on transaction end it must be stored as well. In
other words I want my objects to be stored not only in memory, but
also in some file/DB storage. Persistent and reusable objects?
···
–
Best regards,
Eugene [team Enticla] mailto:Eugene.Scripnik@itgrp.net
Eugene Scripnik wrote:
I am searching for the application/server that allows to store
objects and easy manipulate them. It must support caching,
transactions and loading by request, so if I loaded some object and
want to access some subobject it must be automaticly loaded from DB.
I’m working on a Ruby interface to the GOODS object database:
http://www.garret.ru/~knizhnik/goods.html
Eventually, I’d like to refactor RubyGOODS to be a generic,
transactional object persistence/sharing library that could use
pluggable drivers to support various back ends such as flat files or
relational databases.
Unfortunately, I’m working on a pretty heavy-duty contract right now and
it could be a little while before I finish the GOODS interface, let
alone the generic object persistence library.
RubyGOODS can be found at:
http://sourceforge.net/projects/ruby-goods
although I haven’t put anything there yet due to being stuck behind a
stringent firewall.
···
–
Jason Voegele
“We believe that we invent symbols. The truth is that they invent us.”
– Gene Wolfe, The Book of the New Sun
Friday, November 1, 2002, 5:47:54 AM, you wrote:
Eugene Scripnik wrote:
I am searching for the application/server that allows to store
objects and easy manipulate them. It must support caching,
transactions and loading by request, so if I loaded some object and
want to access some subobject it must be automaticly loaded from DB.
I’m working on a Ruby interface to the GOODS object database:
http://www.garret.ru/~knizhnik/goods.html
Eventually, I’d like to refactor RubyGOODS to be a generic,
transactional object persistence/sharing library that could use
pluggable drivers to support various back ends such as flat files or
relational databases.
Unfortunately, I’m working on a pretty heavy-duty contract right now and
it could be a little while before I finish the GOODS interface, let
alone the generic object persistence library.
RubyGOODS can be found at:
http://sourceforge.net/projects/ruby-goods
although I haven’t put anything there yet due to being stuck behind a
stringent firewall.
I am trying to develop such server based on drb, and the main problem
I have encountered is marshalising connected objects (components): I
can’t cut subobject from the main object. Marshal dumps all the object
tree. I think there are two methods of dumping objects in this way.
First one: mark some of them in special way and implement custom
Marshal, that would skip marked objects. The second way is to store
some unique IDs to subobjects instead of objects itself, but there are
a lot of additional code on client side.
···
–
Best regards,
Eugene [team Enticla] mailto:Eugene.Scripnik@itgrp.net