[
https://jira.jboss.org/jira/browse/DNA-309?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-309:
-----------------------------------
The URI design may need to make room for different repositories, workspaces, etc. The
first segment of the URI (below the host or application URI) might specify the repository
name, the second the workspace name, followed by the path to the node. For example:
/repoA/myWorkspace/a/b/c/d
would identify the node "/a/b/c/d" in the "myWorkspace" workspace of
the "repoA" repository configured by the RESTful server.
What about searching? Well, search could be done using the "/search" URI,
making that a reserved name and unusable for the repository name in the configuration.
That probably is pretty acceptable.
What about a web application for users to view, navigate, edit the content through a
browser? Well, its quite likely that this application would be in a different WAR
(perhaps still deployed to the same server). However, there are two options if the web
app is to be in the same WAR file: reserve the "/ui" URI for this (might be a
good idea anyway), or simply use the HTTP accept header to specify that a client wants the
(probably rich) HTML for a resource.
Design URLs, leaving room for future UI features and maybe WebDAV
-----------------------------------------------------------------
Key: DNA-309
URL:
https://jira.jboss.org/jira/browse/DNA-309
Project: DNA
Issue Type: Sub-task
Components: Web Application
Affects Versions: 0.3
Reporter: Johnny Verhaeg
Fix For: 0.5
For right now, we need URLs for just publishing and un-publishing content.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira