Hi Darren,
On Mon, 24 May 2010, Darren Kenny wrote:
Hmm, does read a little weird ;)
What I am trying to say here is that because the DOC is the center point for
all data regarding an install, it is then possible to use this fact to
generate an XML manifest - and then later, if using this manifest re-create
the DOC from the manifest to re-perform an install.
I'm still confused. Serializing the DOC data into XML and then
snapshotting it should allow us to later re-create the DOC
and re-perform the install. Is that not enough? If it is, then
I'm having trouble seeing the role this XML manifest plays.
Section 3.3 - Should there be an interface that allows
for marking specific child objects as having been instantiated?
I'm thinking specifically in terms of Target instantiation
and Transfer where there may be multiple children to
instantiate.
I don't think that's part of the DataObject class itself since it's specific
to the implementation area - in other words, not all objects need this. As
such, this would probably be something that a Target base-class might have and
allow for sharing among all Target classes.
That would seem to be fine.
Section 4.5.1 - I'm assuming the Engine will be responsible
for bootstrapping the cache in this case as opposed to DC itself?
No, I see it as being done by the Application, which is the one that controls
which snapshot to load for resuming from. The engine will only take regular
snapshots.
So you would have the Application call DataObjectCache.load_snapshot() and then
call
Engine.execute() - the engine will then continue based on the state of the
data in the cache.
Thanks for clarifying that.
Section 4.6.1 - I don't believe the ManifestParser will be
responsible for locating and downloading the manifest. Instead
AI entities such as manifest-locator and service discovery
will be. ManifestServer will just get the manifest handed to
it.
Hmm, you probably know better here - I've never seen these specifically called
out anywhere and that ManifestParser was always the starting point in any of
the other documents I've seen, as such I've always assumed it was the one to
do the loading/sourcing of the manifest.
Perhaps Sarah can clarify?
Thanks,
Alok
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
