incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olemis Lang <ole...@gmail.com>
Subject [BEP-0003] Default URL mapping WAS: [Apache Bloodhound] Proposals/BEP-0003 modified
Date Tue, 20 Nov 2012 07:59:43 GMT
I have described how we could provide support for many different URL
mappings , and explained the implications .

Nonetheless ...

On 11/20/12, Apache Bloodhound <bloodhound-dev@incubator.apache.org> wrote:
> Page "Proposals/BEP-0003" was changed by olemis
> Diff URL:
> <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=18>
> Revision 18
> Comment: [BEP-0003] External environment routes (using Routes framework)
> Changes:
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
> Index: Proposals/BEP-0003
> =========================================================================
> --- Proposals/BEP-0003 (version: 17)
> +++ Proposals/BEP-0003 (version: 18)
> @@ -94,6 +94,58 @@
>
[...]
> +
> +=== Administration commands #admin-cmd
> +
> +The following new [TracAdmin administration commands] will be implemented
> +
> +||= Command =||= Parameters =||= Description =||
> +|| `deploy-multiproduct` || '''TODO''' || In a way similar to built-in
> ''deploy'' command it will extract environment assets and create scripts for
> [#url-mapping default deployment] via CGI, FastCGI or mod_wsgi. ||
>

In here I'd like to insert a reference to the default URL mapping
deployed OOTB e.g. after executing Bloodhound installer . So we need
to figure out which one will be more appropriate .

[...]
>  }}}
>
>    - [=#deploy-sibling-paths] '''Product path namespace''' : Each product is
>
> @@ -267,7 +325,50 @@
>
>  This case is very similar to the [./MultienvParentDir reference
> multi-environment setup] .
>
> -'''TODO'''
> +Considering the [#routes enhanced routing mechanism] the following routes
> definition will be suitable for single-environment installations
> +
> +{{{
> +#!py
> +
> +>>> from wsgiref.util import setup_testing_defaults as wsgi_environ
> +>>> from routes import Mapper
> +>>> m = Mapper()
> +>>> m.connect(None, '/path/to/bloodhound/{product}/{path_info:.*}')
> +>>> m.match('/path/to/bloodhound/product1/ticket/1')
> +{'action': u'index', 'product': u'product1', 'controller': u'content',
> 'path_info': 'ticket/1'}
> +
> +}}}
> +

I was thinking of installing this one by default ...

> +If the global environment will be treated as yet another sibling product
> environment
> +
> +{{{
> +#!py
> +
> +>>> from wsgiref.util import setup_testing_defaults as wsgi_environ
> +>>> from routes import Mapper
> +>>> m = Mapper()
> +>>> m.connect(None, '/path/to/bloodhound/global/{path_info:.*}',
> product='')
> +>>> m.connect(None, '/path/to/bloodhound/{product}/{path_info:.*}')
> +>>> m.match('/path/to/bloodhound/global/ticket/1')
> +{'action': u'index', 'product': u'', 'controller': u'content', 'path_info':
> 'ticket/1'}
> +>>> m.match('/path/to/bloodhound/product1/ticket/1')
> +{'action': u'index', 'product': u'product1', 'controller': u'content',
> 'path_info': 'ticket/1'}
> +
> +}}}
> +

[...]

... or maybe this one .

What d'u think ?

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Mime
View raw message