Grant, let me see if I can expand this, as it were:
{!benson f1:v1 f2:v2 f3:v3} (or do I mean {!query defType='benson' ...}?)
I see how that could expand to be anything else I like.
However, the Function side has me a little more puzzled.
The information from the fields inside my {! ... } gets
On Apr 3, 2012, at 12:37 PM, Benson Margulies wrote:
> On Tue, Apr 3, 2012 at 12:27 PM, Grant Ingersoll wrote:
>>
>> On Apr 3, 2012, at 9:43 AM, Benson Margulies wrote:
>>
>>> I've made a RequestHandler class that acts as follows:
>>>
>>> 1. At its initialization, it creates a StandardRequest
On Tue, Apr 3, 2012 at 12:27 PM, Grant Ingersoll wrote:
>
> On Apr 3, 2012, at 9:43 AM, Benson Margulies wrote:
>
>> I've made a RequestHandler class that acts as follows:
>>
>> 1. At its initialization, it creates a StandardRequestHandler and hangs onto
>> it.
>> 2. When a query comes to it (I c
On Apr 3, 2012, at 9:43 AM, Benson Margulies wrote:
> I've made a RequestHandler class that acts as follows:
>
> 1. At its initialization, it creates a StandardRequestHandler and hangs onto
> it.
> 2. When a query comes to it (I configure it to a custom qt value), it:
> a. creates a new query
I've made a RequestHandler class that acts as follows:
1. At its initialization, it creates a StandardRequestHandler and hangs onto it.
2. When a query comes to it (I configure it to a custom qt value), it:
a. creates a new query based on the query that arrived
b. creates a LocalSolrQueryReque
