My system only needs a single source per page (it fetches holdings info for
inclusion in a form), but I think you could get a concurrent effect by using
map:aggregate as your generator, with a bunch of internal pipelines to
handle the various input sources. Or if that's not flexible enough, generate
a bunch of xinclude statements and resolve them in a single step. (I'd be
happy to send a sample pipeline if it would help). But I'm not sure of the
Cocoon internals to be sure these operations would be truly concurrent. Art?

Peter


> -----Original Message-----
> From: Kevin S. Clarke [mailto:[log in to unmask]]
> Sent: Tuesday, March 09, 2004 03:36 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] index of open access journals
>
>
> On Tue, 2004-03-09 at 09:09, Binkley, Peter wrote:
>
> > I'm doing some screen-scraping these days for a one-off
> project, using
> > Cocoon to fetch HTML and tidy it into XHTML, then a
> stylesheet to pull
> > out the bits of data that I want. It's all very easy to put
> together
> > as a pipeline
>
> This is interesting to me since I am doing a metasearch
> project right now that requires screenscraping.  I'm curious,
> is the fetching part of this run concurrently or does it have
> to do one resource then the next, etc.
>
> Thanks, Kevin
>
> --
> Kevin S. Clarke ([log in to unmask])
> Digital Information Systems Developer
> Lane Medical Library, Stanford University
>