Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification.
The "Development/NestedFilesystem" page has been changed by jboynes: https://wiki.apache.org/tomcat/Development/NestedFilesystem?action=diff&rev1=3&rev2=4 sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "=" pct-encoded = "%" HEXDIG HEXDIG }}} - where the {{{authority}} component is used to contain the URI of the Path to the archive. Any characters not allow in a {{{reg-name}}} (specifically including "/" and ":") will be pct-encoded. + where the {{{authority}}} component is used to contain the URI of the Path to the archive. Any characters not allow in a {{{reg-name}}} (specifically including "/" and ":") will be pct-encoded. As an example, the entry {{{com/example/Main.class}}} located in the archive {{{/tmp/example.jar}}} whose Path has the URI {{{file:///tmp/example.jar}}} would have the URI {{{ archive:file%3a%2f%2f%2ftmp%2fexample.jar/com/example/Main.class @@ -93, +93 @@ == ToDos == * a way to read the zip’s central directory * a way to seek into a deflated zip entry without inflating the entire thing - * is a ClassLoader from a list of Path helpful? + * is a !ClassLoader from a list of Path helpful? * how to deal with the locking model on Windows platform * how to work with Paths that are directories - do we get this for free? - * how to use the WatchService to detect changes e.g. web.xml or *.jsp touched? + * how to use the !WatchService to detect changes e.g. web.xml or *.jsp touched? == Performance Measurements == TBD @@ -106, +106 @@ == Zip Handling == The JDK API dealing with Zip archives have not been updated to work with the NIO File APIs: - * ZipFile's constructor only accepts a java.io.File or a String relating to a file on the default filesystem + * !ZipFile's constructor only accepts a java.io.File or a String relating to a file on the default filesystem * A zip entry may only be accessed as a sequential !InputStream rather than a !SeekableByteChannel * A !ZipInputStream may only be constructed over an !InputStream rather than a !SeekableByteChannel --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
