First let me say, I can’t program, nor do I fully understand the RT
architecture… That said, I was wondering if any of the following ideas
Could the query builder page and pick lists, be preloaded via the mason
interpreter under modperl? (There seems to a mason option)
One could also try using mason caching for the the picklists, (Mason
does have a caching mechanism) We would just have to add cache control
code to the RT GUI areas that could modify the picklist entries…
Information Technology Dept
Message: 2Date: Sat, 8 Jan 2005 16:52:11 -0500
From: Andrew Sullivan email@example.com
Subject: Re: [Rt-devel] 3.4.0rc1 slow
Content-Type: text/plain; charset=us-ascii
I’d love to see suggestions about how we can improve the search UI
without completely breaking it for users of downlevel browsers. (Which
Well, the problem here seems more to be the number of round trips.
One of my DB guys is looking at how the queries could be altered to
get more in one go, but he’s convinced that it needs a great deal of
work to solve.
right out.) Would people be satisfied if the pick lists for users and
groups were transformed into text entry widgets?
I think that’d just create a new problem, that you’d end up with
groups and users that are typos.
Andrew Sullivan | firstname.lastname@example.org
The plural of anecdote is not data.