> Tore Eriksson wrote:
> > Hello everybody,
> >
> > As I found a solution to my problem, I thought I would share it in case
> > someone else comes up against the same issue. The reason for the client
> > not acting on the redirect is that sendRedirect does not s
ve already
> > committed the response.
> >
> > To achieve what I think you are trying to achieve would require you to
> > create some mechanism where the lucene query results are processed in a
> > separate thread and your application makes TWO requests - one for the
ve would require you to
> create some mechanism where the lucene query results are processed in a
> separate thread and your application makes TWO requests - one for the
> first set of results and then one for the final set of results.
>
> There are far too many different ways
s that the intermittant redirect is not committed until the
function returns, which will take quite some time for some queries. I
have tried HttpServletResponse.flushBuffer() and other possible
variations. Any pointers would be most appreciated.
Tore
_
