#3328: Error display regression 0.9->0.10 (no more HTML errors, just text)
---------------------------+------------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: cboos
Type: defect | Status: assigned
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: review |
---------------------------+------------------------------------------------
Comment (by cboos):
Replying to [comment:8 cmlenz]:
> ... trying to avoid the session and HDF stuff ...
While I agree there could probably be a simpler approach to do this,
I remind you that this was introduced for not having to do those
relatively expensive initializations for every ''/chrome'' request. A
normal Trac request ends up in a dozen secondary requests for images, css,
javascript. Each of them used to trigger that whole setup sequence, for
nothing, if not for making sure you'd trigger a `database is locked`
error... (due to the `authenticate` step, setup of the `PermissionCache`
and setup of the `Session` object).
So this has to be kept in mind when redesigning it, maybe by having a
different category of request dispatchers.
--
Ticket URL: <http://trac.edgewall.org/ticket/3328#comment:9>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
