I've been working on BEP-0003 recently , adding some routes we should support and why . Some details still missing on the subject , especially how all this will work in the context of product environments .
... read below ... On 11/19/12, Apache Bloodhound <[email protected]> wrote: > Page "Proposals/BEP-0003" was changed by olemis > Diff URL: > <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=14> > Revision 14 > Comment: [BEP-003] Sample product URL mappings TODO: Detailed request > dispatching > Changes: > -------8<------8<------8<------8<------8<------8<------8<------8<-------- > Index: Proposals/BEP-0003 > [...] > > '''FIXME''' also be addressable through the product URL namespace, namely > /ticket/<product prefix>/<local ticket id>. > [...] > +In a multi-product configuration product resources should not be accessed > using current global URL scheme (i.e. > /path/to/bloodhound/<environment>/<realm>/<id>). Since [#permissions > products will have their own permissions schema] then requests handled by > components in the context of the top-level environment will perform neither > the right permissions checks nor even use appropriate settings , and so on > ... The same will happen for resources moved between products . In general > such requests should be redirected to a URL under the namespace of > resource's product. > Since proposed solution consists in replicating multi-environment setup inside a single environment formerly proposed URL template (i.e. /ticket/<product prefix>/<sequence ID>) seems not to be appropriate for request dispatching, filtering and other processes taking place in the context of product environments. Therefore I'm proposing to move it to «Rejected ideas» section . I look forward to your comments for feedback . -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article:
