aboutsummaryrefslogtreecommitdiffstats
path: root/COPYING.MIT
blob: fb950dc69feb8afa93493747f33d6e1c02659b55 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Permission is hereby granted, free of charge, to any person obtaining a copy 
of this software and associated documentation files (the "Software"), to deal 
in the Software without restriction, including without limitation the rights 
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
copies of the Software, and to permit persons to whom the Software is 
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 
THE SOFTWARE.
agic */ .highlight .il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */ }
Some notes on features under discussion or consideration, and some
vague implementation thoughts:

* Add some kind of filter for "the directory we care about"
  - pseudo operations would only go to the server for items
    in this directory
  - optionally, logging could be generated for accesses
    *outside* this directory
  - intent is to reduce server load dramatically, and improve
    and/or streamline the logging path when, e.g., doing
    host contamination checking
  - probably implies a new message type, MSG_LOG.

* Database recovery/reconstruction
  - capability for failing harder in the event of apparent
    corruption

* Log database performance improvements
  - some way to do "live" queries against the log database
    while the server is running
  - some way to flush unwanted data
  - possibly a way to separate logging into multiple files
    or otherwise restrict the amount of stuff produced
  - logging filters of some sort

* Canonicalization speedups
  - possibly implement some kind of cache of directory names
    and known canonicalizations

* Possibly limited handling for extended attributes
  - specifically, the case where they're used to manpulate or
    query the plain old modes ala chmod/stat.

* Test cases
  - boy, do we need test cases!

* Clean up *at() functions
  - The *at() function implementations are gratuitously complicated,
    I believe because they predate the auto-canonicalization that came
    with the rewritten pseudo wrappers.