| Feed Contents | |||
|---|---|---|---|
| NGram Index | by wolf | 22-4-2009 20:22 | |
| Installer should ask for data directory | by wolf | 22-4-2009 20:22 | |
| Versioning Support | by wolf | 28-2-2009 12:39 | |
| Refactor HTTP Interfaces | by adam | 16-12-2008 16:33 | |
| XFormsFilter | by adam | 16-12-2008 16:25 | |
NGram Index
- Support for simple wildcard queries, e.g. ngram:contains(para, 'abcd?f')
- proximity: find 'abc' near 'def'
- similarity search: 'live' finds 'lives', 'life', ...
- 0 Comments
- Add Comment
Installer should ask for data directory
By default, eXist creates its data directory in EXIST_HOME/webapp/WEB-INF/data. On windows, this means that the data dir is located below the Program Files directory. While this is usually ok for Unix (Apple?) users, Vista doesn't really like it when users are writing data into Program Files (it creates a shadow dir if you are not an administrator).
The installer should ask for an alternate location for the data directory, maybe depending on the OS type.
Refactor HTTP Interfaces
A refactoring of eXists HTTP Interfaces - EXistServlet, RESTServer, SOAPServer, WebDAV.
Benefits
- Upgrade to Jetty 6
- Make use of NIO (take lessons from Apache MINA)
- Simplify and reduce the code
- Improve testability
- Allow easy extensibility
- Simplify control and configuration
XFormsFilter
The XFormsFilter provided with eXist allows integration with an older version of Chiba and provides XHTML output support for Chiba. The XFormsFilter concept has now been adopted by Chiba as their preferred access method.
We need to investigate whether Chiba is still an active and relevant implementation of XForms and if so a new integration with Chiba should be provided.
Open Tasks for Chiba Integration
- Analysis of Chiba viability
- Contributions to Chiba's XFormsFilter to support operation without additional Servlets
- Build scripts for integrating eXist and Chiba
- Documentation
