[Rt-devel] RE: Rt-devel Digest, Vol 10, Issue 7

Brian_Gupta at timeinc.com Brian_Gupta at timeinc.com
Sun Jan 9 15:28:20 EST 2005

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
make sense:

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... 

Brian Gupta
Time Inc
Information Technology Dept

Message: 2
Date: Sat, 8 Jan 2005 16:52:11 -0500
From: Andrew Sullivan <ajs at crankycanuck.ca>
Subject: Re: [Rt-devel] 3.4.0rc1 slow
To: rt-devel at lists.bestpractical.com
Message-ID: <20050108215211.GA16581 at phlogiston.dyndns.org>
Content-Type: text/plain; charset=us-ascii

On Sat, Jan 08, 2005 at 04:01:56PM -0500, Jesse Vincent wrote:
> 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  | ajs at crankycanuck.ca
The plural of anecdote is not data.
		--Roger Brinner


More information about the Rt-devel mailing list