Not totally sure what you mean, but I guess you mean that each user has its own color code.
Then I guess the procedure I mentioned would still work, but you'd need one color file per user (i.e., "colors_user1234.xml"). If I'm way off-base here, just let me know. Like the other person said, this is something best handled in a database. You'd have 1 config record per user in a table. With XML, you have to re-write an entire file, not just change a record. The best way I can think of to do that without having a big performance hit is to have 1 user_config.xml per user and just completely re-write it when needed. DR At 10:25 PM 11/20/01 +0000, you wrote: >Apologies my point was that I want users to be able to enter a code >themselves which would then become permanent. > >-----Original Message----- >From: David Rosenstrauch [mailto:[EMAIL PROTECTED]] >Sent: Tuesday 20 November 2001 19:43 >To: [EMAIL PROTECTED] >Subject: Re: Accepting Data From The Web and storing it. > >I imagine you'd have to write some custom code - most likely an Action >object I would guess - that gets executed when they submit the form. >The Action would have to manually re-write that file with the new color >info. > >One thing that might be helpful is to have a separate XML file with just >the color info in it, and just overwrite that. e.g.: > ><colors> > <color value="6699cc"/> ></colors> > >Then your style sheet can reference the contents of this file using the >XSL document() function. e.g.: > ><xsl:variable name="color" select="document('color.xml')/colors/color"/> > > >I use this in my site, although for a different reason. I wanted to >have all the colors listed in a separate XML file so that I could easily >change any or all of them. > > >HTH. > >DR > > > >At 05:31 PM 11/20/01 +0000, you wrote: > >Hi after finally gripping the fundamentals and basics of the publishing > >framework of cocoon 2, I would now like to take this a step further and > >implement a system but I have a question. > > > >Using XML, XSP, XSL, XSL:FO, SVG I can publish pages but how would I go > >about using cocoon2 to save data back to the same XML, XSP files the > >pages were the data was first taken from. So for example an XSP file > >creates an XML file that is piped to an XSL file and then transformed >to > >make a picture of a clock. On this page would also be a form to edit >the > >clocks colour by supplying an SVG colour. The problem I am having is >how > >to write the colour back to the original XSP file so that the colour > >changes permanently. > > > >Thanks for your time > > > >Sharat Koya > > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]> >For additional commands, e-mail: <[EMAIL PROTECTED]> > > > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]> >For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
