Skip to content

Cache results of parsing URI parameters #982

Open
szeiger opened this Issue Apr 21, 2011 · 6 comments

5 participants

@szeiger
szeiger commented Apr 21, 2011

Menu.param allows you to define a parser and an encoder for a URI parameter. The parser is a good place to retrieve an item from a database and automatically get a 404 if it is not found, but the parsing is performed multiple times per request and the result is not cached. As a workaround, you can manually thread the result through a RequestVar. It would be nice to have a caching Menu.param available in Lift out of the box.

@indrajitr
Lift Web Framework member

Updating tickets (#919, #938, #950, #956, #976, #980, #982, #999, #1008, #1024, #1025, #1032, #1034, #1051)

@indrajitr
Lift Web Framework member

Updating tickets (#950, #956, #976, #980, #982, #999, #1008, #1053, #1078, #1092, #1097)

Pushed pending tickets to 2.4-M5

@indrajitr
Lift Web Framework member

Updating tickets (#956, #976, #980, #982, #1008, #1053, #1078, #1092, #1097, #1128)

@indrajitr
Lift Web Framework member
@dpp dpp was assigned Mar 1, 2012
This was referenced Mar 1, 2012
@Shadowfiend
Lift Web Framework member

This actually came up again on the list the other day—is the idea here that we would stick the results of the parse in a TransientRequestVar?

@Shadowfiend Shadowfiend assigned Shadowfiend and unassigned dpp May 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.