One more option: Do you really need to wait to start the lengthy
process for when there's a user there, or can you do most of it ahead of
time, periodically, in the background? The latest results get cached.
Then, when a user comes to your site, you can tailor the output of the
latest cached info - presentation, content filtering, etc. This is what
I did at:
http://www.rule-of-eight.com/
A background thread periodically starts the lengthy process of
retrieving and parsing metadata from other sites, and builds an object
model which is cached. Then, when the page is requested, a filtered
html presentation is generated on the fly from the latest cached info.
The client always gets up-to-date info, and there's no response delay.
I've found that using the Decorator pattern really helps here. Similar
to the how the java.io.Reader/Writer classes work.
- Robb
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
