> Maybe it is a bit harsh, but I think I stand by it. I know > what deadlocks are, and now how to avoid them in MarkLogic > Server. I just think that in a service-oriented software > package that, by design, will crash in the event of X (taking > all other App Servers, WebDAV and XCC connections with it), > then X shouldn't necessarily be available by default. The > developer should explicitly (as if signing a consent form) > say "I know what deadlocks are, I understand the risks, I > won't crash the server, promise."
One additional note to what Ian already said. The deadlock will only occur in Xqueries using xdmp:eval or xdmp:invoke etc. It can not occur from WebDav (not sure about XCC though). Note also that it is only between the transaction calling evaluate string and the transaction opened for that particular evaluation. Ciao Drs. G.P.H. Josten Consultant http://www.daidalos.nl/ Daidalos BV Source of Innovation Hoekeindsehof 1-4 2665 JZ Bleiswijk Tel.: +31 (0) 10 850 1200 Fax: +31 (0) 10 850 1199 http://www.daidalos.nl/ KvK 27164984 De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend. _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
