<div dir="auto">I’m not sure there’s much contention anymore. X3D and glTF both support binary (AFAIK) or at least EXI (see X3DJSONLD website) and UTF-8. Obviously ASCII-only doesn’t really fly for an ISO standard.</div><div dir="auto"><br></div><div dir="auto">One can start with simple data and add complexity later. Profiles…</div><div dir="auto"><br></div><div dir="auto">I am fairly sure the standardized? fetch() method can do a lot for at least client-server communication. I don’t know if it can push tons of data though, such as video, which is why WebRTC is preferred for peer-peer communication.</div><div dir="auto"><br></div><div dir="auto">AJAX can be overly complex, but I doubt if people are doing live video over AJAX. Prove me wrong.</div><div dir="auto"><br></div><div dir="auto">I believe that Discord and VS Code are built with similar technology. I think that Electron may be a preferred technology stack now. YMMV</div><div dir="auto"><br></div><div dir="auto">Check out glTF extensions for VS Code!</div><div dir="auto"><br></div><div dir="auto">Perhaps the easiest thing to do would be to integrate X3DOM and X_ITE into VS Code? Or just use a pre-existing VRML extension? Michalis, do you have some info on VRML and CGE in VS Code?</div><div dir="auto"><br></div><div dir="auto">As Ballmer said, “Developers, developers, developers”</div><div dir="auto"><br></div><div dir="auto">John</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 16, 2022 at 3:13 AM Christoph Valentin <<a href="mailto:christoph.valentin@gmx.at">christoph.valentin@gmx.at</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Hi Vince, Hi all,<br>
<br>
Thank you for this additional information.<br>
<br>
Finally I have found the original e-mail I was referring to: it was written by Leonard D. on Mon Mar 11 07:48:58 PDT 2019.<br>
<br>
Citing Leonard D.:<br>
<br>
Subject: Network Sensor & Protocols<br>
<br>
[...]I chaired the Networking Sensor WG many years ago. There was a <br>
fundamental disagreement as to what should be passed between clients -- <br>
whether it was real simple data (e.g., position, orientation) in a data <br>
structure understood by agreement of the clients (mostly because the one <br>
person wrote all code) or a more general structure that handled a <br>
variety of data types. Other contentious points were binary vs. ASCII <br>
(now UTF-8/16) or perhaps something else; and whether the communication <br>
required a server or was strictly between clients (browsers). The <br>
simplest case amounted to the Network Sensor being a wrapper around the <br>
operating system's socket interface.<br>
<br>
However it is decided, any X3D Network Sensor will need to be compatible <br>
with WebRTC when X3D is running in the web browser if the Network Sensor <br>
is to run between clients or AJAX if running between client and server. <br>
There are many restrictions and/or conventions that need to followed or <br>
handled. Two of them are: 1) The port needs to be compatible with <br>
corporate firewalls (pretty much restricts to 80 and 443, though some <br>
others are available). 2) If the communication is to the server, then <br>
the design needs to take into account CORS (Cross-Origin Resource Sharing).<br>
<br>
Leonard Daly[...]<br>
<br>
Question: is it still valid?<br>
<br>
<br>
Thanks,<br>
Christoph<br>
<br>
<br>
Gesendet: Freitag, 15. April 2022 um 16:33 Uhr<br>
Von: "<a href="mailto:vmarchetti@kshell.com" target="_blank">vmarchetti@kshell.com</a>" <<a href="mailto:vmarchetti@kshell.com" target="_blank">vmarchetti@kshell.com</a>><br>
An: "Christoph Valentin" <<a href="mailto:christoph.valentin@gmx.at" target="_blank">christoph.valentin@gmx.at</a>>, "X3D-Public" <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
Cc: "Kevin" <<a href="mailto:klw71@yahoo.com" target="_blank">klw71@yahoo.com</a>><br>
Betreff: Re: [x3d-public] X3D/VRML Multiuser - WebRTC/AJAX<br>
<br>
Joe Williams posted this to x3d-public on Mar 10 2022.<br>
It references an implementation rather than a standards decision by the X3D Working Group<br>
<br>
Vince Marchetti<br>
<br>
<br>
<br>
<br>
Found from 06, <br>
<br>
<a href="https://web.archive.org/web/20160328040324/http://www.hypermultimedia.com/ajax3d/index.htm#Start[https://web.archive.org/web/20160328040324/http:/www.hypermultimedia.com/ajax3d/index.htm%23Start]" rel="noreferrer" target="_blank">https://web.archive.org/web/20160328040324/http://www.hypermultimedia.com/ajax3d/index.htm#Start[https://web.archive.org/web/20160328040324/http:/www.hypermultimedia.com/ajax3d/index.htm#Start]</a><br>
<br>
to<br>
<br>
<a href="https://web.archive.org/web/20160331112316/http://hypermultimedia.com/ajax3d/T0.htm%5Bhttps://web.archive.org/web/20160331112316/http:/hypermultimedia.com/ajax3d/T0.htm%5D" rel="noreferrer" target="_blank">https://web.archive.org/web/20160331112316/http://hypermultimedia.com/ajax3d/T0.htm[https://web.archive.org/web/20160331112316/http:/hypermultimedia.com/ajax3d/T0.htm]</a><br>
<br>
and the rest, <br>
where x3d in object could use XMLHttpRequest client/server interface when hosted by DOM browser. <br>
<br>
Since Tony did such a great exercise in the original out of MediaMachines, I “made it mine” and did a Joe version. <br>
<br>
Amazing, looks like it still all there and almost works except no Hello because no Flux Player™, and looks like canvas has solid support over object or iframe? Is the XMLHR a thing? <br>
Old Fun,<br>
Joe _______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>[mailto:<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>]<br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
On Apr 15, 2022, at 3:20 AM, Christoph Valentin <<a href="mailto:christoph.valentin@gmx.at" target="_blank">christoph.valentin@gmx.at</a>[mailto:<a href="mailto:christoph.valentin@gmx.at" target="_blank">christoph.valentin@gmx.at</a>]> wrote: <br>
<br>
Dear all,<br>
<br>
I am sorry to bother you again with this topic.<br>
<br>
I remember someone (was it Joe?) wrote at the mailing list about a decision of the consortium:<br>
If a Web3D scene is hosted by a browser, then the communictation for multiuser features shall be done via WebRTC and AJAX.<br>
<br>
Unfortunately, I cannot find the mail any more in the archives. Could someone point me to that mail? Or could you confirm that remembrance?<br>
<br>
Thanks,<br>
Christoph<br>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>[mailto:<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>]<br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
</blockquote></div></div>