[Blacklight-development] demo questions

Jamie Orchard-Hays jamie at dang.com
Mon Apr 6 10:30:35 EDT 2009


I'll have a look at the double requests this morning. I can't imagine  
why we're doing it.


On Apr 5, 2009, at 6:54 AM, Erik Hatcher wrote:

> On Apr 4, 2009, at 12:01 PM, Matt Mitchell wrote:
>> [1:16pm]erikhatcher:next, GETing that page causes two requests to  
>> Solr:
>> [1:16pm]erikhatcher:Apr 3, 2009 1:15:50 PM  
>> org.apache.solr.core.SolrCore execute
>> [1:16pm]erikhatcher:INFO: [] webapp=/solr path=/select  
>> params={id=2008308478&qt=document&wt=ruby} hits=1 status=0 QTime=1
>> [1:16pm]erikhatcher:Apr 3, 2009 1:15:50 PM  
>> org.apache.solr.core.SolrCore execute
>> [1:16pm]erikhatcher:INFO: [] webapp=/solr path=/select  
>> params 
>> = 
>> {wt 
>> = 
>> ruby 
>> &rows 
>> = 
>> 1 
>> &start 
>> =1&facet=false&fq=geographic_subject_facet:"China"&fl=*&qt=search}  
>> hits=1 status=0 QTime=1
>> [1:16pm]erikhatcher:what's with that second request for 1 row?
>>
>> Ok, so why does one request to a Blacklight detail page result in  
>> two requests to Solr?   That can't be necessary, or right, no?
>>
>> Yeah, to figure out what is next and previous. Might be a better  
>> way to do this?
>
> I'll have to ponder on that.  It doesn't seem right to have the  
> counter on the URL or to make two requests to Solr to show a detail  
> record.  Exactly what information is needed for previous/next?



More information about the Blacklight-development mailing list