Hi again Günter, >Just saw, that you’ve also written a node-based Basex-Client
There are quite a few https://www.npmjs.com/search?q=basex >Are there any advantages (disadvantages) to change to a classical Server-Client Scenario I think it all depends what you want to do. I wrote my client before RESTXQ existed, now I find I can do (almost) everything I want from BaseX. So my client has not had much attention recently and it's handling of streaming and various edge cases could certainly be improved. If I was looking to connect Node and BaseX now I would look at an http interface to RESTXQ, but this may not be the most performant, resource light option. /Andy On 3 April 2016 at 21:46, kleist-digital <kle...@mail.dunzwolff.de> wrote: > Hi Andy, > > me again. Just saw, that you’ve also written a node-based Basex-Client. My > frontend is a node-app. So far I’m using AJAX-calls, to communicate via the > REST-Interface with the Basex-Server, in generell I use the run command to > execute different queries. > > Are there any advantages (disadvantages) to change to a classical > Server-Client Scenario (performance, less resources, security)? You know, I > want to use it in an OpenShift-Environment for the future. > > Thanks for any advice. > > Günter >
