Re: xindice usage
"Tak-po Li" <[email protected]> Mon, 22 Sep 2008 13:30:17 -0400
| Newsgroups | gmane.text.xml.xindice.user |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_37176_2043011.1222104617782 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 > ------=_Part_37176_2043011.1222104617782 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <div dir="ltr"><div> </div> <div>Natania, </div> <div> </div> <div>It seems node level is similar to the record level in relational DB.</div> <div>Thanks for your new info.</div> <div> </div> <div>Tak</div> <div> </div> <div> </div> <div><br><br> </div> <div class="gmail_quote">On Mon, Sep 22, 2008 at 9:02 AM, Natalia Shilenkova <span dir="ltr"><<a href="mailto:[email protected]">[email protected]</a>></span> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div class="Ih2E3d">On Sat, Sep 20, 2008 at 4:11 PM, Tak-po Li <<a href="http://takpo.li/" target="_blank">takpo.li</a>@<a href="http://gmail.com/" target="_blank">gmail.com</a>> wrote:<br>><br>> Hi Natania,<br> ><br>> Thanks, I will change the PATH from /db/addressbook to /db/cad.<br>><br>> Change the subject again. I am new with xml database. How it can be used<br>> in a typical web application? What is a typical way to handle multiple<br> > users and version control?<br><br></div>I don't think that using Xindice as database would be so much<br>different from relational DB. Access/version controls have to be<br>implemented in an application - there is no such built-in<br> functionality in Xindice.<br> <div> <div></div> <div class="Wj3C7c"><br>> I am working on an online CAD tool that would serve multiple users with<br>> programmable group read/write access allowance (similar to file access in<br>> Unix system) and version control. On the surface, the xml database can be<br> > setup as following:<br>><br>> /db/<br>> cad/<br>> group0/<br>> user0/<br>> proj0/<br>> page0/<br>> page1/<br> > page2/<br>> ...<br>> proj1/<br>> ...<br>> user1/<br>> proj0/<br> > page0/<br>> page1/<br>> page2/<br>> ...<br>> proj1/<br>> ...<br> > user2<br>> ...<br>> group1/<br>> ...<br>><br>> How should I handle programmable access? should I use attribute in the<br>> project level to handle it? What is minimum unit for an update? Should we<br> > handle update in the page level or could it be done in even lower<br>> level? How should I implement version control in that case?<br><br></div></div>XUpdate service allows to modify documents on the node level. As for<br> the rest of the questions... It's not like there is only one way of<br>doing something like that. And the answer depends on lots of things<br>that you probably know better than anyone else. Good luck :)<br><br>Regards,<br> Natalia<br><br>><br>> Thanks,<br>><br>> Tak<br></blockquote></div><br></div> ------=_Part_37176_2043011.1222104617782--