Right, I wasn't thinking of a replacement, just that this seems like missing information that is available at the callout location that should be passed through. Best regards,
- Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) ----- Original Message ----- > From: lars hofhansl <[email protected]> > To: "[email protected]" <[email protected]> > Cc: > Sent: Sunday, January 29, 2012 3:23 PM > Subject: Re: Difference between coprocessors and filters > > Sure. Although I am not sure whether coprocessors should actually do that. > They > can operate on top of a scanner that is already filtered by a filter. > I think that would need a completely new API. > > > -- Lars > > > ________________________________ > From: Andrew Purtell <[email protected]> > To: "[email protected]" <[email protected]> > Sent: Sunday, January 29, 2012 11:09 AM > Subject: Re: Difference between coprocessors and filters > >> Seek-hints could be added to coprocessors - preScannerNext/postScannerNext > -, but they do not currently support this.) > > Coprocessors shouldn't be a catch-all for every extension case, but this is > arguably missing information that should be passed through. File a JIRA for > it > Lars? > > Best regards, > > - Andy > > > On Jan 28, 2012, at 8:53 PM, lars hofhansl <[email protected]> wrote: > >> Seek-hints could be added to coprocessors - preScannerNext/postScannerNext > -, but they do not currently support this.) >
