Submitting content to OMBase and logging

While I was reading up on the REST papers in my last post, I stunbled upon the following best practice for making sure that material is only submitted once to a RESTful application. This is something we should adopt in OMBase as well, just to be safe.

Another thing that we should think of in this  arena is to enable some form of RESTful logging facility, so that users can find out what happened to the content. The technology that seems best suited for that seems to be RSS or Atom Syndication (probably the latter). The nice thing is that we could log all the changes to any URI we use in the system. I am not sure under which URL we would address the log, one idea is to just make use of the the mime type application/atom+xml just as for the xhtml presentation as suggested in my last post that would at least alleviate the choice of URL.

2 Responses to “Submitting content to OMBase and logging”

  1. In itself this is probably not that useful, compared to the great idea of downloading presented HTML. The genereated feed should contain links to older versions of the resources, and for that we need an extension to the URL syntax, e.g. sth. like GET path/to/document?version=13 – and this should also be supported for any other content type.

  2. kohlhase says:

    you are right, the old versions should be accessible (in our current setup, they can be retrieved from the underlying subversion repository, in Slava’s version they can be served natively.

Leave a Reply

You must be logged in to post a comment.