cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <vadim.gritse...@verizon.net>
Subject Re: DOM Protocol, Was: Revised ResourceLoadAction posted...
Date Tue, 18 Nov 2003 12:30:05 GMT
danielf@nada.kth.se wrote:

>Vadim Gritsenko wrote:
>  
>
>>My initial though was to have following syntax:
>>
>>   dom:[request|session|context]:<attribute-name>#<jxpath>
>>
>>Xpath, and '#' symbol is obviously optional, and '#' was chosen for 
>>    
>>
>consistency with existing xmldb: protocol.
>
>I like the "#" part, but all the ":" looks strange to me. I prefer 
>thinking of the attribute type and the attribute name as a hierarchy:
>
>      dom:/[request|session|context]/<attribute-name>#<jxpath>
>
>or are there other examples of protocols that use ":" in the way that  you
>propose?
>  
>

Sure! :)

   jdbc:oracle:thin: ...
   xmldb:xindice: ....


>I make the DOMSource XMLizable so that one can read XML in an efficient 
>way from it, (like in e.g. the XMLDBSource and QdocsSource).
>

Cool.


>Do you know 
>if there is some prefered mechanism for makeing modifyable sources SAX 
>writable. In Cocoon 2.0 there existed an interface
>o.a.c.components.source.WritableSAXSource, that had a method for
>returning a content handler, for such purposes. I have not found
>anything similar in Cocoon 2.1. Should I make the DOMSource an
>XMLConsumer or just don't care about it and only use an otput stream?
>  
>

Hmmm... Just don't care about it now -- if anything, it will be fixed later.

Vadim




Mime
View raw message