Re: [basex-talk] Concurrency WebDAV vs. REST API

On 10 Jan 2019, at 6:53, Christian Grün wrote: >> >> This is not true. > > > Sounds like a communication problem. My impression is that we are both > right. Did you read our documentation? The documentation perhaps does not explain the behavior properly. but anyway… A write operation in any

Re: [basex-talk] Concurrency WebDAV vs. REST API

On 9 Jan 2019, at 20:48, Christian Grün wrote: >> Are you saying that a write transaction blocks pending READ requests > until the transaction > has been committed? > > No. What I was trying to say is that we deliberately designed REST requests > to be atomic transactions. If you perform

Re: [basex-talk] Slow WebDAV operation

On 9 Jan 2019, at 20:39, Christian Grün wrote: >> >> Please check the log entries..there are only HEAD/PROFIND/GET requests >> on the WebDAV level against a single XML resource. >> > > I just created a collection with 120,000 documents. The time for retrieving > a single resource was about 100

Re: [basex-talk] Slow WebDAV operation

On 7 Jan 2019, at 11:20, Christian Grün wrote: > The WebDAV implementation is definitely not the one that provides best > performance in BaseX. Nevertheless, I think I’ll have a look at the > use case you describe. Some questions in return: > >> I re-verified the behavior on a third (fast)

Re: [basex-talk] Concurrency WebDAV vs. REST API

on. In order to preserve the ACID > principles, no other operations will run in parallel. If you want to > run concurrent operations, you should be fine if you send your > commands one by one via multiple REST requests. > > Best > Christian > > > On Fri, Jan

Re: [basex-talk] Slow WebDAV operation

I re-verified the behavior on a third (fast) machine with SDD and the result as still bad with an average of 900-1000ms per request. Andreas On 4 Jan 2019, at 12:13, Andreas Jung wrote: The original tests below have been made on a virtualized machine with 8 cores, 64 GB RAM. My first idea

Re: [basex-talk] Slow WebDAV operation

:44.346127.0.0.1:35556 admin 200 1700.02 ms Andreas On 4 Jan 2019, at 11:37, Andreas Jung wrote: I have an optimized database with 25K objects, 8 GB of data running on 9.1.1. WebDAV operations are very slow (client running and connecting locally). The response times

[basex-talk] Slow WebDAV operation

I have an optimized database with 25K objects, 8 GB of data running on 9.1.1. WebDAV operations are very slow (client running and connecting locally). The response times are by a magnitude slower compared to exist-db. Is there some something missing in the configuration in order to speed this up

[basex-talk] Concurrency WebDAV vs. REST API

For development purposes I am running basehttp in foreground. The WebDAV endpoint seems to block while I run a larger import for REST with lots of ADD and STORE commands within one .. section. The WebDAV connection times out…what is the explanation for this? Andreas signature.asc Description:

[basex-talk] Setting modification timestamp (for content migrated over WebDAV) over REST?

As part of a migration we move data into BaseX over WebDAV. It would be neat if we could preserver the original timestamp. I am aware that it is not possible to set the timestamp over WebDAV. Would it be possible to set the modified timestamp for particular resource over the resource API or is

Re: [basex-talk] Bulk import (moving from eXist to BaseX)

/770a4a0e0b34de5250d0ce54a4e509ec -aj On 1 Jan 2019, at 16:21, Andreas Jung wrote: > Hi there, > > consider moving my XML stuff for a particular project from eXist to BaseX. > > I have a full dump from eXist with all related content and I want to import > it 1:1 > into BaseX…is there

[basex-talk] JSON serialization/compatibility with exist-db JSON?

Hi there, I have an issue with the migration of an XQuery script from eXist to Basex: The link https://gist.github.com/zopyx/467a01264d53bdaa48ad27cd553cfda8 shows the script and the expected (status quo) output for XML and JSON. Calling the script using /rest/foo/?run=foo.xql=json

[basex-talk] Bulk import (moving from eXist to BaseX)

Hi there, consider moving my XML stuff for a particular project from eXist to BaseX. I have a full dump from eXist with all related content and I want to import it 1:1 into BaseX…is there a bulk loader or what is the preferred way to import an existing folder structure? Of course I can create

[basex-talk] Strategies for using BaseX & friends as XML CMS?

Hi there, we are currently investigating options for using XML database as a backend in a publishing project related to technical documentation - DITA in particular. The broad customer requirements are checkin and checkout of documents, locking of documents and versioning. Has anyone worked

Re: [basex-talk] State of replication and clustering

üngliche Nachricht- > Von: basex-talk-boun...@mailman.uni-konstanz.de > [mailto:basex-talk-boun...@mailman.uni-konstanz.de] Im Auftrag von Andreas > Jung > Gesendet: Dienstag, 1. August 2017 15:12 > An: BaseX > Betreff: [basex-talk] State of replication and clustering &

[basex-talk] State of replication and clustering

Hi there, what is the state of replication and clustering of BaseX? I found an XML Prague 2013 presentation but almost no documentation on these topics on the website. In our case we need to scale out horizontally with a growing number of reads (no writes involved). Andreas signature.asc

[basex-talk] Deployment of BaseX on Windows in Service Fabric?

Hi there, has anyone experiences with deploying BaseX in Azure Service Fabric on a Windows node either as Guest Executable or Windows Container? Andreas signature.asc Description: OpenPGP digital signature

Re: [basex-talk] Atomic replacement of documents with a collection

Thanks Christian, sound all good to me. Andreas On 1 Aug 2017, at 11:45, Christian Grün wrote: > Hi Andreas, > >> Is REPLACE atomic in the sense that an >> ongoing request will see the „old“ state of the document and new requests >> will >> see the new state of the document without any

[basex-talk] Atomic replacement of documents with a collection

Hi there, I am finally heading for the first time to use BaseX in a customer project. We need to import XML based product catalogs in different languages. The catalog files should be updated each night without service interruption. What is the best strategy to update and replace an existing

Re: [basex-talk] Installation of RESTXQ scripts over HTTP API?

could be theoretically used to transfer the files, e.g. ssh, ftp or I guess also WebDAV is the RESTXQ-directory is used by some WebDAV server (excuse me if this is totally wrong, I have never used WebDAV, but it should work somehow...). Cheers, Dirk On 08/24/2015 07:39 AM, Andreas Jung wrote

Re: [basex-talk] Installation of RESTXQ scripts over HTTP API?

08:19 AM, Andreas Jung wrote: Background: http://xml-director.info/ is my project which aims to support both ExistDB and BaseX. In ExistDB I can manage my content, assets and code (RESTXQ) scripts solely over the WebDAV layer of ExistDB which makes deployments really easy. Deploying code

Re: [basex-talk] non-ascii collection names over WebDAV?

is done within the Milton library. As far as I know, eXist-db uses the same WebDAV library; did you encountered the same encoding issues with eXist-db? On Fri, Aug 21, 2015 at 9:32 AM, Andreas Jung li...@zopyx.com wrote: Hi there, does BaseX support the creation of collections containing non

[basex-talk] Installation of RESTXQ scripts over HTTP API?

Hi there, I know that .xqm script are installed directly on the filesystem (compared to Exist where the scripts are stored directly within the database). Is there some way to install RESTXQ through some (HTTP) API on the filesystem? Background of my question: I want to deploy RESTXQ script to

Re: [basex-talk] non-ascii collection names over WebDAV?

I could reproduce this using cadaver dav:/webdav/ ls Listing collection `/webdav/': collection is empty. dav:/webdav/ mkcol üöäß Creating `üöäß': succeeded. dav:/webdav/ ls Listing collection `/webdav/': succeeded. Coll: uoas and using Python 2.7 (using pyfilesystem API). Andreas On 21

[basex-talk] non-ascii collection names over WebDAV?

Hi there, does BaseX support the creation of collections containing non-ascii (uft8-encoded) characters? In my case we have a functionality to import a ZIP file into BaseX or Exist-DB over WebDAV. File names and directory names must be preserved. BaseX seems to normalize names to ascii. Any

Re: [basex-talk] Modelling Checkin-Checkout using locks

Christian Grün wrote: I have added a GitHub issue on your locking request [1]. In the meanwhile, it's probably best to use RESTXQ (XQuery) and check if a resource is locked before returning it to a user. [1] https://github.com/BaseXdb/basex/issues/1083 Thanks. Meanwhile I started working on

[basex-talk] Modelling Checkin-Checkout using locks

Hi there, I am currently thinking about ways how to model a reliable checkout-checkin scenario with XML documents. In an older SGML CMS system that we build, we implemented the procedure roughly like that: - user chooses a document in the CMS and clicks on CHECKOUT - CHECKOUT copy the document

Re: [basex-talk] Modelling Checkin-Checkout using locks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 oops, this was intended for the exist-db guys...but the question are similar...anyone used BaseX with a checkout-checkin scenario? Andreas Andreas Jung wrote: Hi there, I am currently thinking about ways how to model a reliable checkout

[basex-talk] WebDAV Lock error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, some more WebDAV issues (tested against the 8.1 snapshot from yesterday). - - connecting with cadaver and locking a file twice causes a HTTP 500 error on the cadaver side and BaseX fails with this exception: [qtp2029686239-17] INFO

Re: [basex-talk] Lock issue while editing a .xql script over WebDAV

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Grün wrote: And finally fixed. Somewhere, a timeout was set to Long.MAX_VALUE, leading to an out of bounds exception. A new snapshot is available. confirmed, works now. Thanks Andreas -BEGIN PGP SIGNATURE- Version: GnuPG

Re: [basex-talk] Debugging RESTXQ scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Grün wrote: It works on my machine. Did you specify an Accept header in your request? I would expect it to be mandatory in eXist db as well.. curl -HAccept:application/json http://localhost:8984/all-documents.json; Gotcha, existdb

Re: [basex-talk] Debugging RESTXQ scripts

Andreas Jung wrote: Christian Grün wrote: Both scripts (my own and the hello world script) are located inside a 'scripts' subfolder: dav:/webdav/scripts/ ls I'm a bit surprised about the 'webdav' segment in you path. Is this a sub-directory of the webapp directory (please see [1] for more

Re: [basex-talk] Debugging RESTXQ scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Grün wrote: curl -HAccept:application/json http://localhost:8984/all-documents.json; This now returns the XML version of func() - however now JSON serialized response although %output:method(json) is specified!? Since Version 8.0,

Re: [basex-talk] Debugging RESTXQ scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Grün wrote: This is the script that serializes to (XML), JSON and HTML in existdb https://gist.github.com/zopyx/eee05f7a421a6c0b6b80 Thanks. I guess it follows the conversion rules described in [1]? My broader goal is to figure

Re: [basex-talk] Debugging RESTXQ scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Grün wrote: The result is XML-ish, try yourself: curl -HAccept:application/json http://dev1.veit-schiele.de:8984/all-documents.json My expectation is receiving a JSON string. This is how the XQuery spec wants it to be. If you

Re: [basex-talk] Debugging RESTXQ scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Grün wrote: This was the missing link for moving a script from exist-db to BaseX. A more complete example in the docs would be helpful here. To get a better understanding, could you give me a small example how eXist converts XML to

Re: [basex-talk] Debugging RESTXQ scripts

Jup, in existdb you can treat RESTXQ scripts like data and throw it directly into the database instead of separating code from data like in BaseX..but thanks for clarification. Regards Andreas Jung - Sorry for being brief - sent from a mobile device. Am 17.02.2015 um 21:31 schrieb

Re: [basex-talk] Debugging RESTXQ scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Grün wrote: Both scripts (my own and the hello world script) are located inside a 'scripts' subfolder: dav:/webdav/scripts/ ls I'm a bit surprised about the 'webdav' segment in you path. Is this a sub-directory of the webapp

Re: [basex-talk] Debugging RESTXQ scripts

/tmahDbBTrjEGxJ jnhkifviGhn4eRNukPf/3ZHAa5CI96X/ANtJrsyL3zMJ5KPresMUtJZ9sftit9kx bq2oqA8E+hmDzO2snFpPflDjdOUd5ABUcYMrGx7lqOVQNTOzRatBAH3dqpmQjZLb ha5S7yApyT7+3Lk841bNiTUH3zItPJQ= =iWtX -END PGP SIGNATURE- - -- Regards Andreas Jung andr...@andreas-jung.com about.me/andreasjung

[basex-talk] Debugging RESTXQ scripts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I moved the following (under existdb 2.2 working) script to BaseX https://gist.github.com/zopyx/eee05f7a421a6c0b6b80 Calling the script gives me a 404. The hello world example script from the BaseX docs however works. So general

[basex-talk] Lock issue while editing a .xql script over WebDAV

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, the following bug occurs while re-editing a .xql script. - - start cadaver against the WebDAV port - - inside cadaver: edit some.xsql and save an empty file - - re-edit the same file again and this LOCK related issue pops up Cheers

Re: [basex-talk] Python client and BaseX 8.0

- -- Regards Andreas Jung andr...@andreas-jung.com about.me/andreasjung -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJUoVsUAAoJEADcfz7u4AZjWoILwMUkypGYOB8N9NPenIXNCZaD

[basex-talk] User has already been assigned. and 500s errors with Docker

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I am experimenting with Docker and BaseX 8 (snapshot of yesterday). I wrote my own Dockerfile https://github.com/zopyx/docker-basex and create my own Docker image https://registry.hub.docker.com/u/zopyx/basex80/ My WebDAV test suite

Re: [basex-talk] User has already been assigned. and 500s errors with Docker

are covered pretty well). I will look into that. Sorry for the circumstances. Christian On Thu, Dec 11, 2014 at 10:15 AM, Andreas Jung li...@zopyx.com wrote: Hi there, I am experimenting with Docker and BaseX 8 (snapshot of yesterday). I wrote my own Dockerfile https://github.com

[basex-talk] XML-Director project announced

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, please allow me to announce a new toy project XML-Director of mine that will be powered by eXist-db or Base-X. https://www.andreas-jung.com/contents/announcing-the-xml-director-xml-cms-project http://www.xml-director.info Andreas

Re: [basex-talk] XML-Director project announced

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Grün wrote: Andreas, thanks for the announcement, looks exciting! Keep us posted if you expect certain features in BaseX that would further simplify the integration. Transaction support across arbitrary operations :-) Andreas

[basex-talk] WebDAV issue in BaseX 8, how to track down

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I have a bunch Python code that runs with unittests perfectly against exist-db. However I have some issues with the WebDAV implementation of Base-X (tested against the latest 8.0 beta snapshot). In my case I am trying to read a file that

Re: [basex-talk] Bug in 7.9: REMOVE over WebDAV not working

in advance, Christian [1] http://files.basex.org/releases/latest On Sat, Nov 1, 2014 at 12:40 PM, Andreas Jung li...@zopyx.com wrote: Hi there, removing a folder/collection over WebDAV does not work. The problem can be easily reproduced by creating a folder/collection using 'cadaver

Re: [basex-talk] Bug in 7.9: REMOVE over WebDAV not working

/5b624b0da5b317c9f802d1cfd0befca336f5a834 On Sat, Nov 1, 2014 at 12:40 PM, Andreas Jung li...@zopyx.com wrote: Hi there, removing a folder/collection over WebDAV does not work. The problem can be easily reproduced by creating a folder/collection using 'cadaver' and then trying to remove it. I was also able