#1 Burning Software

Hello,

As part of my incremental DVD update strategy I would like to maintain an index file (index.xml) on the DVD to reflect some business data about the other files that are present.

Ideally I would be able to update this index.xml file by doing something like this:

* StarBurn_ISO9660JolietFileTree_ImportTrack() to pull the existing track, including existing index.xml.

* StarBurn_ISO9660JolietFileTree_GetFirstKid() / StarBurn_ISO9660JolietFileTree_GetNamesEx() / StarBurn_ISO9660JolietFileTree_GetNextKid() to search the imported tree and find the tree node represetning the old index.xml

* StarBurn_ISO9660JolietFileTree_Remove(old index tree node)

* StarBurn_ISO9660JolietFileTree_Add(new index file from hard drive)

...and procede to BuildImage and TrackAtOnceFromTree.

Can you tell me if this is feasible? Or in general perhaps once I write a certain-sized file out to a track it is not practical to delete that file and write out a new version to a different spot. I understand the DVD isn't a fully-flexible file system with fragmentation ability...just not sure how far the capability goes for the sort of update I want to do.

Thanks!
Chris

This is really not required to have everything so complex. During adding the file with the same name (index.xml) you'll get collision callback. All you need is set collision action to NAME_COLLISION_REPLACE_OLD and you'll have NEW node with the same name in the final compilation. That's all