IN THEORY, EJB containers are better able than Tomcat to spread
incoming requests over a multitude of servers. There was considerable
discussion some time ago about index search speed on a single
processor. I do not remember the details, but there was some
information about how fast a search might be expected to go with one
processor.
If that is fast enough, Tomcat should suffice.
My search application has a few short documents so my experience is not
relevant.
On Oct 12, 2006, at 10:46 AM, mark harwood wrote:
EJB explicitly precludes you from accessing files, including via third
party libraries such as Lucene.
http://java.sun.com/blueprints/qanda/ejb_tier/restrictions.html
In practice you may be able to get away with it but I see no
particular reasons why using an EJB server should offer any benefits
over a Servlet container.
Cheers
Mark
----- Original Message ----
From: "Chenini, Mohamed " <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Thursday, 12 October, 2006 3:25:44 PM
Subject: a design question
Hello,
This is a design question: For Lucene to be able to process a million
documents and in the purpose for the search application to be scalable
and still have a good response time do we need to use an EJB container
such as Weblogic or is a Servlet container such as Tomcat sufficient to
do the job? This design should take into consideration remote
searching.
Thanks,
Mohamed
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
Send instant messages to your online friends
http://uk.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
