xml-axkit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From daro...@apache.org
Subject cvs commit: xml-axkit TODO
Date Sun, 24 Mar 2002 02:53:01 GMT
darobin     02/03/23 18:53:01

  Modified:    .        TODO
  Log:
  Added a few TODO entries for consideration
  
  Revision  Changes    Path
  1.8       +17 -0     xml-axkit/TODO
  
  Index: TODO
  ===================================================================
  RCS file: /home/cvs/xml-axkit/TODO,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- TODO	12 Mar 2002 19:10:15 -0000	1.7
  +++ TODO	24 Mar 2002 02:53:01 -0000	1.8
  @@ -84,6 +84,15 @@
       provider that uses an XML DB on the backend.
   
   
  +  . Separate Provider for stylesheets
  +
  +    It would appear that one of the main problems people have when using new
  +    providers is that stylesheets are also looked up through them, which
  +    causes various problems to people. One (backcompat) way of doing this
  +    would be to have it still work this way if no AxStyleProvider is setup,
  +    but AxStyleProvider would be able to override AxProvider.
  +
  +
     . More control on the interaction between the configuration and PIs
   
       Some would like it to be possible to use both the configuration and PIs
  @@ -116,3 +125,11 @@
       a user must either do processing of that element himself or rely on a particular
   	module's implementation. Moreover, in XSP difficulties can arise. Having a
   	global xml:lang policy would make multi-language support easier.
  +
  +  . Binary data support
  +
  +    It's easy to be beaten when dealing with binary support in AxKit. It should be 
  +    possible to flag one's output (at *any* stage) as binary, and have 
  +    binary-unsafe operations (such as char conversion, xml parsing, etc.) be
  +    skipped.
  +
  
  
  

Mime
View raw message