On Sun, Mar 28, 2010 at 8:44 AM, Ilya Skorik <[email protected]> wrote: > > Hello. > > I plan to use jackrabbit in a Web application. Prompt, what strategy is > necessary for selecting for the connection organisation to base? >
There are many options. Actually, it seems that a lot of people are running the repository inside the webapp. My team insists on a server style deployment of the repository, and I found that the spi/davex remoting is the most robust at this time; perhaps it's even considered the preferred remoting method. See: http://wiki.apache.org/jackrabbit/RemoteAccess Note, there's an RMI method on that same page but it's considered to lack production performance, and, in Jackrabbit 2.0, it's not even fully implemented. > Considering specificity of Web applications when the server handles set of > queries from different users. > > Whether there is something like connection pooling for jackrabbit? > -- > View this message in context: > http://n4.nabble.com/Jackrabbit-and-web-application-tp1694146p1694146.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. >
