LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

*** empty log message ***

This commit is contained in:
david 2001-09-25 23:39:37 +00:00
parent 37cd137e31
commit 05b26e39e1
2 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
LDP/scrollserver/CHANGELOG
View File

@ -5,6 +5,7 @@ Unreleased 0.6 ScrollKeeper access is locale aware
Malcolm: Content-length header
Malcolm: kill FileContents()
Malcolm: proper __init__ clause
More hacking documentation
2001-09-23 0.5 Moved internal cache files to cache root.
Handle anchors (#foo) in URIs.

15
LDP/scrollserver/HACKING
View File

@ -64,12 +64,13 @@ it will have to support man pages, info pages, and other formats.
Documents in html are served, but they look different from the DocBook documents
because we don't generate them ourselves. There is no navigation bar on the top,
for example, and they don't use my stylesheets. There is a bit of ad-hockery
for example, and they don't use my stylesheets. There is a bit of ad-hackery
involved in serving documents that are physically distributed through a common
uri scheme so they appear to be part of a single tree.
There is no support for processing documents that are stored remotely. That's a
good todo item for somebody.
good todo item for somebody. It's pretty trivial using urllib. Unfortunately,
ScrollKeeper doesn't yet support them.
Searching
@ -82,11 +83,15 @@ A huge problem in all help systems is finding the needle in the haystack that
will answer your problem. So, the search engine has to have a big focus to make
ScrollServer an indispensable tool on your desktop.
I want to look into using XQuery for remote document queries, but it is a new
proposal and so it is changing rapidly. Perhaps it is best to put that off for
a bit until it stabilizes. RDF might be part of a good solution.
Other Possibilities
-------------------
Just about any other web based service you can imaging could be implemented in
Just about any other web based service you can imaging could be implemented and
integrated into ScrollServer, including message boards on the various topics.
XLink provides for creating links from document A to document B from within
@ -94,3 +99,7 @@ Document C, along with many other powerful ways of associating data. A user
could conceivably write a `post-it' style notee on their document, and share
that note with other readers of the document, where it could be accepted or
rejected or edited by others. There are many other possibilities as well.
If I decide to go with a URN based scheme for these additional services, they
could even be implemented as plugins.