Jeremy Quinn wrote:
> 
> At 3:51 pm +0100 26/11/01, Giacomo Pati wrote:
> >Quoting Berin Loritsch <[EMAIL PROTECTED]>:
> >
> >> Ugo Cei wrote:
> >>
> >> > Giacomo Pati wrote:
> >> >
> 
> >> > - write a Source (this I hadn't even figured until I read Giacomo's
> >> >   mail)
> >
> >This is nothing I thought of doing.
> 
> This is something I have been discussing with Sylvain and others.
> 
> I have been trying to write an RT about it .......
> 
> For instance (yeah, sorry I am crap at these diagrams!). This could be an
> XSP Generator or XSP Action (the request data should already have been
> validated by a previous Action):
> 
> Request
> 
> |
> 
> |
> XSP:Capture[file.xml] --{DOM}--> XSP:XUpdate[with user data] --{DOM}-->
> XSP:Write[file.xml]
> 
> Where :
> 
> "XSP:Capture" is the Capture TagLib (or similar) fed by SAX events from (in
> this case) a FileGenerator "WritableSource" which has the capability to
> temporarily "lock" the source during the transaction.
> 
> "XSP:XUpdate" would be the XUpdate standard written as an XSP TagLib,
> receiving, manipulating and outputting a DOM or SAX Events.
> 
> "XSP:Write" represents "releasing" the "WritableSource" which in this case
> results in the modified DOM being written back to file and the lock being
> released.
> 
> The idea is to provide similar functionality to the old FP Cocoon 1 TagLib,
> but (this time) to disassociate the XML manipulation from the source or
> destination, so that the modified XML could be written to file, sent to
> SQL, Castor, stored temporarily in the user's session, whatever.

I'm happy you bring this on the table because I was thinking about the
best way to make this client-side editor connect with a solid
repository.

But I don't think I understood your diagram above :)

Can you restate?

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<[EMAIL PROTECTED]>                             Friedrich Nietzsche
--------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to