-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I wanted something like this maybe nine months ago and ended up creating
my own @RequestParameter annotation, overriding Form, ActionLink,
EventLink, and PageLink, and modifying the way Tapestry generates URLs.

It works, but it ain't pretty. Anyway, back then, it looked like
something like this would be easy enough to implement using a
persistence strategy, it would just require some changes to many aspects
of URL handling in Tapestry - for one, I remember needing access to the
name of the page a Link was for.

I think that it would be worthwhile, though - the activation context is
great for a lot of things, but as you can tell from this thread, you
sometimes need the flexibility offered by request parameters - and that
is currently way too hard (compared to how easy most things are) in
Tapestry.

/Filip

On 2009-05-09 00:29, Robert Zeigler wrote:
> That should work.
> I think it could be interesting, though, if tapestry provided an
> additional persistence mechanism, ala:
> 
> @Persist(PersistenceConstants.QUERY_PARAMETER)
> private String p;
> 
> @Persist(PersistenceConstants.QUERY_PARAMETR)
> private Integer irn;
> 
> which would then take the values in p and irn and stash them in the url,
> like:
> p=<valueEncodedValue>&irn=<valueEncodedValue>
> 
> Obviously this wouldn't be appropriate to use everywhere; if you're
> concerned about users tampering with URLs, you'd want to avoid it.
> But in cases like that presented below, where you expressly want users
> to be able to muck about with parameters, it would be useful.
> 
> Note that this is similar to the current client-side persistence
> mechanism, except that mechanism a) rolls all persisted values into a
> single parameter and b) base64 encodes the parameter.
> 
> As long as you've got the basic mechanism for doing the above, you could
> translate it into a "pretty" url via url rewriting without too much
> trouble.
> 
> Thoughts?
> 
> Robert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJKCsjVAAoJEEfiH7PpjaMnWbIIAJdAPuQo5jngCCZt2DSXV5e3
dGG+0wOOnxrmC2jFTDrxVRvWx7dfA4hGuAFPQgz/USP+NviNkEvFz2iGfZTAgmzA
19BFLfx1AdWYu2ft1tPULkBGmxaLa/Rjt0qosHn3+kKo+Kgl0yhDjcZSbx29+Ic6
8eBRn0krOha5o6GU6OU/iIqMEjRvErAOutB63nlRr7oIfuttffucPXDGE0UutQ9v
llwzlQoGfk5ywHr0AqJlclA0AH44ePOtxiP4xg3OwgVh9Wge/vHMVGxYURzbp/lf
wvqTP3iASZHOYEYpji6/J31awC/3T8gcP+Rm/53VLrDtsU2dHnfzJ+B7hJpjYAk=
=SYe3
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to