tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Callender <geoff.callen...@mac.com>
Subject Re: [jira] Created: (TAP5-264) Lack of direct support for named context parameters
Date Mon, 13 Oct 2008 09:51:44 GMT
Absolutely - just go to the issue and click on Comment. If you can't  
log in it's no problem to create an account.

On 13/10/2008, at 8:45 PM, Joel Halbert wrote:

> Would it be possible to add a comment to this request along the  
> lines of:
>
> "Can we investigate using the @Persist("client") notation as a way  
> of transparently storing named parameters across sessions, much in  
> the same way as is done now, but with human friendly query string  
> encodings for primitive types"
>
> Such that if one declares
>
> @Persist("client")
> String name;
>
> then rather than it being encoded on to the query string as  
> "asjklnckjsndc09dc09j23oirnm3lknmsdcm.smdc"  (etc .... !)
> it is simply encoded as "name=value" (or some similar variant, where  
> ideally the encoding strategy can be user defined)
>
> I hope this makes sense...!?
>
> (I would add the comment myself but I believe only developers can do  
> this?)
>
> Thx,
> Joel
>
>
>
> Francois Armand (JIRA) wrote:
>> Lack of direct support for named context parameters
>> ---------------------------------------------------
>>
>>                 Key: TAP5-264
>>                 URL: https://issues.apache.org/jira/browse/TAP5-264
>>             Project: Tapestry 5
>>          Issue Type: Improvement
>>    Affects Versions: 5.0.16
>>            Reporter: Francois Armand
>>
>>
>> T5 "REST" orientation make easy the mappin between url and  
>> resources, but it lack the possibility to add "normal" named  
>> parameters.
>>
>> This one are quite handy when one's want to make big queries  
>> bookmarkable. For example, in a application that send email to  
>> dynamic mailing list build as the result of a search in the company  
>> user base, it would be great if each user can bookmark his most  
>> used filter/dynamic ml.
>>
>> The implementation can fit quite well with the current T5  
>> implementation if we add a direct mapping of the kind :
>> In URL map=[string=string,string=string] becomes a  
>> Map<String,String> in onActivate. I think that we can limit the use  
>> of Map<String,String> (at least for 5.0).
>>
>> For example :
>> http://foo/myT5app/mypage/normalcontext/ 
>> mycontextmap=[key1:value1,key2:value2]/othercontextparam
>> => in the Java code :
>> void onActivate(String normalcontext, Map<String,String>  
>> mycontextmap, String othercontextparam) {
>>  String username = normalcontext:
>>  String telephone = mycontextmap.get("key1"); //let the user handle  
>> the type
>>  String email=mycontextmap.get("key2");
>>  String eqalityType=othercontextparam;
>>  ....
>> }
>>
>>
>
> -- 
> SU3 Analytics Ltd
> 61b Oxford Gardens
> W10 5UJ
> London
>
> Tel: +44 20 8960 2634
> Mob: +44 75 2501 0825
> www.su3analytics.com
>
> SU3 Analytics Ltd is a company registered in England and Wales under  
> company number 06639473 at registered address 61b Oxford Gardens,  
> London W10 5UJ, United Kingdom.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message