Hi Damon, Thank you for the clarification.
Gary From: [email protected] [mailto:[email protected]] On Behalf Of Damon Feldman Sent: Monday, May 23, 2011 2:43 PM To: General MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] FW: WebDAV latency Gary, MarkLogic uses a set of mimetypes (configurable in the admin console) that determine when a document is binary vs. XML vs. text. For example, if you have HTML, some of it may be valid XML but most won't. Based on the mimetype, they will all be saved as text by default rather than have the system put in some as XML and some as text. Ingesting using an .xqy module or the Information Studio flows, or with explicit calls to xdmp:document-insert() allows you to explicitly set the content as text, binary or XML, if your extension is not doing the right thing, but I don't think webdav can be configured that way. Yours, Damon From: [email protected] [mailto:[email protected]] On Behalf Of Gary Larsen Sent: Thursday, May 19, 2011 2:35 PM To: [email protected] Subject: [MarkLogic Dev General] FW: WebDAV latency It appears that WebDAV requires the document id to have a .xml extension as the modified document is being stored as a binary. gary From: Gary Larsen [mailto:[email protected]] Sent: Thursday, May 19, 2011 11:13 AM To: '[email protected]' Subject: WebDAV latency Hi, I'm developing cts queries using Oxygen which uses a WebDAV server for content navigation. It seems that after I edit and save a document (to check query logic), the document can no longer be found with a query, even though it was found prior to the save. Even just adding whitespace to a document makes it 'disappear'. Could someone help be understand this behavior? Is this suppose to happen with WebDAV? How about the XDBC server? Confused, gary
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
