Woops, somehow sent before I intended. Just a sec.
On Tue, Jul 23, 2013 at 1:40 PM, Gerald de Jong ger...@delving.eu wrote:
I'm trying to quickly prototype a REST server which uses BaseX for
persistence using NodeJS.
I'm able to create a session, add a document, query that document, and
So the driver sends a query for something that should give no results:
'\u/somethingNotThere\u'
It then receives, to my surprise:
'\u\u'
followed by:
'1\u\u'
then sends:
'\u00041\u'
and receives again:
'\u\u'
Are these proper responses.. is the driver
Hi Gerald,
Could that '\u\u' be part of an asynchronous response to some
previous command?
Otherwise it looks fine:
- '\u () \u' // create query returning empty sequence
- '1\u \u' //The 1 is the query handle.
- '\u0004 1 \u'//Execute the query with handle
I have created an issue [1] and will take a look this evening. I suspect it
is my problem rather than BaseX. I have never been happy with that parsing
code :-)
I see there are now 3 Node BaseX clients [2] I think Hans simple-basex has
a lot of good ideas regarding the parsing.
/Andy
[1]
4 matches
Mail list logo
