ActionModule

Version 4.1 by Vincent Massol on 2010/01/14 08:17
Warning
For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [dev:XWiki.DesignClassSheet]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

This is a page for deciding what the Action, and the ActionManager should look like. They are already written and are functional although the XWikiServlet which routes requests to the ActionManager is still not activated in the web.xml file.

Summary:

Actions need to be ported out of the old core into their own components. It is important that the new Action model be in place so that newly added actions do not have to be ported as well.

Current Situation:

There is an Action interface, an ActionManager, and an XWikiServlet which work but design is not finished.

Use cases:

  • When a browser supports gzip compression, the response should be passed through a discrete gzip Action component. However if the requested material is already compressed (images), it should not be gzip'd.
  • If the user is not logged in and the action they are requesting does not alter the database (Registration) the request should be passed to a cache Action. If the cache contains the desired page then it is returned, otherwise it is passed on to the requested action and when returned it is added to the cache.
  • If desired, a filter Action may catch requests depending on user agent, ip address etc. And reroute the request. Banned!

Requirments:

Implementation Details:

Get Connected