Tammo van Lessen wrote:
IRequestFilter exists for exactly this reason, and can reroute requests without any changes to the original handler.Noah Kantrowitz wrote:That's why I said 'assume' and not 'claim' ;) The idea of REST includes that a resource has always a single identifier (i.e. URL), no matter which representation is rendered. That means that trac (or a plugin) would need to look at the content negotiation header of the request to then dispatch to a particular representation (be it HTML, RSS, Atom, CSV, JSON..) of this single resource. If there is a way to hook in a plugin that overrides the implementations of IRequestRequestHandler in each trac component (e.g. ticket, wiki,...) to support other representations as well as support for PUT and DELETE it would be certainly possible to write a plugin for such stuff. I just had a quick look at IRequestHandler and it implementation for tickets and I've got the impression that implementing REST is not that easy and not possible without modifying the core. Please correct me if I'm wrong.Tammo van Lessen wrote:Unless you can cite something specific, this is generally an incorrect assumption.Noah Kantrowitz wrote:As with XML-RPC, this will never be part of Trac core, but it would make a great plugin. Go for it! :)I'd love to, unfortunately days are way to short nowadays... Anyways, I'm afraid this stuff cannot be out-sourced into a plugin. I assume that it required some changes in trac's core...
--Noah
signature.asc
Description: OpenPGP digital signature
