Jeremy Quinn wrote: >While working on WritableSourceTransformer, I was going to look at making a >SourceIOTransformer, that would have two verbs : > > <source:write src="" ..... /> > > <source:read src="" ..... /> > >What do you guys think about this? >This is kind of the logical conclusion to the symmetry provided by the new >WritableSource interface. > >It would not completely replace XInclude because it would not be able to do >any caching (?). The transformer in the sitemap has no knowledge of what it > Ok, caching writing does not make sense, I guess, but caching the reads should be possible as the source interface contains a getLastModified()-call that should do the trick, so this partially overlaps with XInclude.
BTW, two aspects: first of all, I find the naming of WriteableSource somehow confusing; what about seperating this into Source and Drain/Sink/whatsoever and changing the "src" attribute into a "dest"-attribute so this makes more sense and prevents accidential damage ? Best regards, Michael Hartle, Hartle & Klug GbR --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
