[x3d-public] X3DJSONLD problem not solved for X3DOM

[John Carlson]

Actually it now appears like my X3DOM version gets frozen, and X_ITE continues, instead of vica versa.  Out of the frying pan and into the fire.   I am going to try the same technique with my DOM version of X3DOM in a bit, to see if I can patch it.    A problem for another day.

Sigh!

If anyone wants to look at it, see

https://coderextreme.net/X3DJSONLD/, or my GitHub repo https://github.com/coderextreme/X3DJSONLD/

It only happens after a few loads from the pulldown.

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Tuesday, March 20, 2018 6:37 PM
To: x3d-public at web3d.org; x3dom mlist
Subject: X3DJSONLD problem solved (for local service)

Thanks to Holger Seelig for providing a starting point on my exploration of X3DOM and X_ITE concurrent operation issues, I was able to solve a long standing issue
with X3DJSONLD and can now provide X_ITE as a reliable service in a local X3DJSONLD instance.  There I still a problem with X3dOM with a web site served by non-express servers that I haven’t discovered yet, but I am presently working on it.  It causes the X3DOM instance to fail  when hosted on a remote site.   A local express site, run with node app.js is fine.  I am happy, because X_ITE does more complex things than X3DOM, like complete protos and VRML scripting, and if I don’t have to continually reload it makes development happier!

Have fun using X_ITE and X3DJSONLD.  Now with no-reloading!

John


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180320/8918abe4/attachment.html>