Natania, It seems node level is similar to the record level in relational DB. Thanks for your new info.
Tak On Mon, Sep 22, 2008 at 9:02 AM, Natalia Shilenkova <[EMAIL PROTECTED]>wrote: > On Sat, Sep 20, 2008 at 4:11 PM, Tak-po Li <[EMAIL PROTECTED]> wrote: > > > > Hi Natania, > > > > Thanks, I will change the PATH from /db/addressbook to /db/cad. > > > > Change the subject again. I am new with xml database. How it can be > used > > in a typical web application? What is a typical way to handle multiple > > users and version control? > > I don't think that using Xindice as database would be so much > different from relational DB. Access/version controls have to be > implemented in an application - there is no such built-in > functionality in Xindice. > > > I am working on an online CAD tool that would serve multiple users with > > programmable group read/write access allowance (similar to file access in > > Unix system) and version control. On the surface, the xml database can be > > setup as following: > > > > /db/ > > cad/ > > group0/ > > user0/ > > proj0/ > > page0/ > > page1/ > > page2/ > > ... > > proj1/ > > ... > > user1/ > > proj0/ > > page0/ > > page1/ > > page2/ > > ... > > proj1/ > > ... > > user2 > > ... > > group1/ > > ... > > > > How should I handle programmable access? should I use attribute in the > > project level to handle it? What is minimum unit for an update? Should > we > > handle update in the page level or could it be done in even lower > > level? How should I implement version control in that case? > > XUpdate service allows to modify documents on the node level. As for > the rest of the questions... It's not like there is only one way of > doing something like that. And the answer depends on lots of things > that you probably know better than anyone else. Good luck :) > > Regards, > Natalia > > > > > Thanks, > > > > Tak >
