documentation question

> http://docs.basex.org/wiki/JAX-RX_API

Am 15.11.2011 um 17:31 schrieb C. M. Sperberg-McQueen: > For complicated reasons, one of the copies of BaseX I am working with > at the moment is (as far as I can tell) version 6.7; is there a convenient > way to find the 6.7 documentation on the BaseX site? Or should one > just read the current documentation and be prepared to ignore all the > material marked as new in 7.0? I'm particularly interested in reading up on > the http interface, which I know has changed a lot in 7.0. > > At some point, I expect that that copy of BaseX will be upgraded to > version 7, but for now if I want to work with that copy, I need to address > it in 6.7 terms. > > Michael Sperberg-McQueen

On Nov 15, 2011, at 10:12 AM, Michael Seiferle wrote: > Dear Michael, > > sorry for inconvenience, but in 6.7 the only http API that has been available for HTTP was our JAX-RX implementation. > Thus most of our current documentation covers features not available in 6.7. > > But, this page covers JAX-RX: >> http://docs.basex.org/wiki/JAX-RX_API > > Anyways I'd suggest updating to 7.0, the http features have changed a lot :-) > > Hope this helped, feel free to ask for more

Am 15.11.2011 um 21:22 schrieb C. M. Sperberg-McQueen: > Thank you; that is precisely the documentation I was looking for.

> > Are there any complications we need to be worried about in moving > from 6.7 to 7.0 in a production database? Or do we just unpack > 7.0 in an appropriate location and change the system startup routines > to call the 7.0 server scripts instead of the 6.7 scripts the next time > we reboot?

Am 16.11.2011 um 17:41 schrieb C. M. Sperberg-McQueen: > > I've just noticed that the Mac OS X app package doesn't contain > the shell scripts for launching the server and command-line client, > etc. I've downloaded BaseX702.zip and can unzip it -- is there a > reliable way to integrate that material into the BaseX.app directory > structure, or should I just install it separately in /opt/local? And > if I do, do I need to be careful not to run the server at the time as > I'm run > ning the GUI app? Or do I only need to be careful if I > am actually changing the databases?

> > Thank you! > > Michael > -- > **************************************************************** > * C. M. Sperberg-McQueen, Black Mesa Technologies LLC > * http://www.blackmesatech.com > * http://cmsmcq.com/mib > * http://balisage.net > **************************************************************** > > > >

On Nov 16, 2011, at 3:20 AM, Michael Seiferle wrote: > Hi, > Am 15.11.2011 um 21:22 schrieb C. M. Sperberg-McQueen: > >> Thank you; that is precisely the documentation I was looking for. > you're welcome :-) >> >> Are there any complications we need to be worried about in moving >> from 6.7 to 7.0 in a production database? Or do we just unpack >> 7.0 in an appropriate location and change the system startup routines >> to call the 7.0 server scripts instead of the 6.7 scripts the next time >> we reboot? > It should work just fine, regarding storage and query evaluation, I'd recommend to have a backup of production data ready anyway. > Additionally I suggest you give it a try before going to production, in the current implementation the URLs and variable binding changed when compared to JAX-RX. > > If you run into any problems please let us know, we are here to help.