No i dont think so What i am suggesting is we have nutch beans instantiated and we store it .
Whenever an user comes and searches ,he will be given a NutchBean . After he searches he returns it to the pool and during the same time when some one searches he would get the same bean (note new bean is not created ) Only if a bean is not available ,does a new bean get created . This makes it faster as different users share the same NutchBean and it does not create a new nutchbean Note:NutchBean is shared across different users whereas right now it is only for a single user and garabage collected Here we control the NutchBean instantiation and we have to come up with a way to free it . On 1/6/06, Byron Miller <[EMAIL PROTECTED]> wrote: > > If i'm not mistaken doesn't the opensearch servlet get > around this issue? You could then post process the xml > through a stylesheet/css or your favorite scripting > language. > > -byron > > --- Raghavendra Prabhu <[EMAIL PROTECTED]> wrote: > > > Right now > > > > Whenever an user comes and searches ,a NutchBean is > > created > > > > We should have a mechanism where this nutchbean is > > pooled .I mean is created > > and stored so that it can be given to the user > > > > Immediately after the user has used the Nutch Bean > > ,he returns it back > > > > (example at orkut ,we get a message saying doughnut > > not available) > > > > This will make search result faster and more > > efficient > > > > Only when paraller users are there will nutchbeans > > get created > > > > Any comments on the above issue > > > > > > Rgds > > Prabhu > > > >
