Hi Marco, hi France,
Thanks for the feedback on creating web sockets. Feel free to tell us
how the BaseX code could be modified to get it embedded more smoothly.
Best,
Christian
On Mon, Oct 31, 2016 at 3:46 PM, Marco Lettere wrote:
> Hi France,
> I can confirm that for
Hi France,
I can confirm that for using websocket you'll have to write some Java
code. That's what we've done for creating a Jetty Connector that is able
to accept websocket connections from HTML5 apps running inside browsers.
Then we interact from inside XQuery by using the mechanism of Java
Thanks Christian,
I feared as much ;-(
I understand the reasoning (processing efficiency and compatibility
with parse-json) but find it unfortunate that backwards compatibility
wasn't part of the reasoning as maps and map:merge are not exactly
new.
--Marc
On Mon, Oct 31, 2016 at 1:50 PM,
Hi Marc,
The reason is why this was decided by the W3C; see [1] and related comments.
Sorry for that,
Christian
[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=29723
On Mon, Oct 31, 2016 at 1:43 PM, Marc van Grootel
wrote:
> Hi,
>
> Any reason why the deault
Hi,
Any reason why the deault semantics for map:merge in 8.6 changed in a
backwards incompatible manner? Is this because of some XQuery/XPath
spec thing? A while ago I switched to 8.6-SNAPSHOT just to be on the
latest and greatest and I starting seeing weird things in my code.
Initially I didn't
Has anyone implemented a solutions that uses web sockets with BaseX? I've
been doing some work with socket.io and node.js, but all the research I've
done on Jetty points to the need to create .java files that manage the
connection on the server side. Does that mean I'd need a BaseX module to
6 matches
Mail list logo