DO NOT REPLY New: - define a consistent sitemap API for all modules that operate on do

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43
989>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43989

           Summary: define a consistent sitemap API for all
modules that
                    operate on documents
           Product: Lenya
           Version: Trunk
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Miscellaneous
        AssignedTo: devlenya.apache.org
        ReportedBy: nettingsapache.org


currently, each module that operates on documents has it's
own way of addressing
them - some use context information from the page envelope,
some have
parameterized matchers, but they are often inconsistent.

i propose the following contract between modules that
operate on documents and
the rest of the world:

any such module must provide

* a context-insensitive (fully parameterized) entry point
that operates on the
document path
* a context-insensitive entry point that operates on a UUID
plus optional
language and revision.

a module can provide
* a context-sensitive entry point that operates on the
current document via the
page-envelope.

all those entry points should be accessible via standardized
matcher patterns.

andreas points out that the matching of document path to
UUID can be factored
out and handled by the global sitemap, where /modules/**
requests are matched.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=ema
il
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the
assignee.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43
989>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43989





------- Additional Comments From solprovidergmail.com
 2007-11-29 03:37 -------
See 1.3 Help:
http://svn.apache.org/viewvc/
lenya/branches/revolution/1.3.x/13HELP.txt?view=markup

The second half of this file defines the content: protocol
used in Lenya 1.3. 
This protocol does everything anybody could possibly desire
for retrieving
documents.  Lenya 1.3's content resources:
- include all types of data: text, xml, and binary
files/records.
- are accessible by uuid/unid or path.
- can specify language.
- can specify revision.

These specifications should be able to replace all local
data access methods.

The protocol is implemented by the o.a.l.cms.content
packages.  The current
packages handle 1.2's hierarchical data structure and 1.3's
flat data structure.
 Can this code be ported to 2.0 with a new package for 2.0's
structure?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=ema
il
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the
assignee.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org