We're getting ready to implement the prototype of a new project and will need to make a semi-final decision about whether to run it as a pure 100% MarkLogic-driven web service (setting up a MarkLogic HTTP server on port 80), or whether to have Apache listen on port 80 and hand things off to MarkLogic as necessary.
In the past, we have done the latter, using httpd.conf to set up virtual hosting and proxying rules such that *.xqy URLs get handed off to MarkLogic while Apache handles *.html?, etc. This was in an environment where we needed to be able to use certain Apache features such as the PHP modules, server-side includes, etc., for legacy PHP/HTML content. The new environment is being designed from the ground up in MarkLogic, so it would seem much more economical and efficient to run only the MarkLogic server. Of course the ML HTTP server isn't as infinitely configurable as Apache (which is maybe a good thing, on the whole). This seems like the way to go, but from other folks' experience are there any considerations that would lead you not to rely on MarkLogic for HTTP service in a single-server environment? David -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: [email protected] Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/ _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
