El lun, 03-04-2006 a las 12:34 +0100, Upayavira escribió:
Thorsten Scherler wrote:
El lun, 03-04-2006 a las 09:00 +0100, Upayavira escribió:
David Crossley wrote:
Upayavira wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Hmm... the current CLI uses
Thorsten Scherler wrote:
El lun, 03-04-2006 a las 12:34 +0100, Upayavira escribió:
Thorsten Scherler wrote:
El lun, 03-04-2006 a las 09:00 +0100, Upayavira escribió:
David Crossley wrote:
Upayavira wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Hmm... the
David Crossley wrote:
Upayavira wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Hmm... the current CLI uses Cocoon's links view to crawl the website. So
although the new crawler can be based on servlets, it will assume these
servlets to answer to a
El lun, 03-04-2006 a las 09:00 +0100, Upayavira escribió:
David Crossley wrote:
Upayavira wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Hmm... the current CLI uses Cocoon's links view to crawl the website. So
although the new crawler can be based on
Thorsten Scherler wrote:
El lun, 03-04-2006 a las 09:00 +0100, Upayavira escribió:
David Crossley wrote:
Upayavira wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Hmm... the current CLI uses Cocoon's links view to crawl the website. So
although the new crawler
Upayavira wrote:
Ah, I wasn't getting that subtle. I was simply saying that I can agree
with using the servlet API for _all_ environments. The CLI becomes
nothing more than a custom servlet container that uses a servlet to
generate its pages.
In fact, having said that, it becomes yet
Sylvain Wallez wrote:
Upayavira wrote:
Ah, I wasn't getting that subtle. I was simply saying that I can agree
with using the servlet API for _all_ environments. The CLI becomes
nothing more than a custom servlet container that uses a servlet to
generate its pages.
In fact, having said
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Hmm... the current CLI uses Cocoon's links view to crawl the website. So
although the new crawler can be based on servlets, it will assume these
servlets to answer to a ?cocoon-view=links :-)
Hmm, I think we don't need the links view in
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
In the case of Forrest, you're probably right. Now the links view also
allows to follow links in pipelines producing something that's not HTML,
such as PDF, SVG, WML, etc.
Yepp.
We have to decide if we want to loose this feature.
Right. So the
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Hmm... the current CLI uses Cocoon's links view to crawl the website. So
although the new crawler can be based on servlets, it will assume these
servlets to answer to a ?cocoon-view=links :-)
Hmm, I think we
Upayavira wrote:
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Hmm... the current CLI uses Cocoon's links view to crawl the website. So
although the new crawler can be based on servlets, it will assume these
servlets to answer to a ?cocoon-view=links :-)
Carsten Ziegeler wrote:
Upayavira wrote:
David Crossley wrote:
Carsten Ziegeler wrote:
I can't speak for Daniel, but my idea/suggestion was to forget about the
different environments and let Cocoon always run in a servlet container.
The CLI would then be kind of a http client which starts up
12 matches
Mail list logo
