Hello all,
This list seems awfully quiet, so I'll post some questions here.
- What's the status on 0.11? I'm confused if it's out or not. I'm
currently developping an app from branches/0.11. This version still
doens't seem fixed, right?
- The new routing is very cool. Quite an improvement on 0.10. Congrats
on that. All in all, the new things I've tested seem to be improvements.
- Performance does seem to be down a bit from 0.10 (haven't done any
benchmarks yet, just an impressions). I'm guessing there'll be some
benchmarking and speed optimization later?
- One problem I have:
my global template contains links to css and js files, like:
<link rel="stylesheet" type="text/css"
href="modpub/css/global.css" media="screen" />
But when the page url gets written using routing (e.g for page
http://test.server.be/apptest/index.php/search), these links are
relative to search and not apptest. How do I solve this? One options is
using href="/apptest/modpub/css/global.css" but this is awkward an means
updating the template when move from one environment to another. There
must be a better option? Should I routing for this also? If so, anyone
have an example?
- How do you handle e.g. the database being unavailable. I could check
everytime a db-connection is acquired and forward/redirect to a
'DatabaseUnavailableAction', but that can get repetitive quickly. For
0.10 I used a filter that did nothing more than catch
'DatabaseUnavailable' or 'GatewayUnavailable' (for external resources
like soap) exceptions, logging them and redirect the user to a nice page
saying that the database is unavailable. Which kind of filter shoud this
be under 0.11? Global or Action? I tried making on, but I couldn't
forward. I got the following exception:
For security reasons, Request Parameters cannot
be accessed directly. Please use the ParameterHolder object passed to
your Action or View execute method to access Request Parameters.
Apparently this happens when the controller tries to add the action to
the actionstack. So I'm guessing I need to unlock the request before
forwarding, or should I redirect? What's the correct way to do this?
Or is there a better way to do some of this global error handling?
Greetings,
Koen Van Daele
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
