[x3d-public] [x3d]V4.0 Opendiscussion/workshopon X3DHTMLintegration

[John Carlson]

I think that “Downloading a big set of scripts” is the wave of the future.  It’s just that you’ll do it for install and updates and not every time you want to run an app.  The app will be installed in your browser, phone or mobile, and you’ll be able to update as desired, or when the content developer wants you to.  JSPs, JSF, Struts (back-end dynamically generated HTML5) etc. will go away, and you’ll be left with JSON, HTTP/WebSockets, REST and perhaps XML across the network.  Network back and forth will actually go down.  The division between Apache for static content and app servers for dynamic content will become more marked.   The thing we want to be able to do is figure out what the standard for dynamic 3D content is.  If it’s just DIS, that’s OK—let’s bring it to the web.  If it’s  SAI, let’s bring that to the web.  Let’s be sure we support H-Anim.  Uh, what else?

John

Sent from Mail for Windows 10

From: Joe D Williams
Sent: Friday, June 10, 2016 3:25 PM
To: doug sanden; x3d-public at web3d.org
Subject: Re: [x3d-public] [x3d]V4.0 Opendiscussion/workshopon X3DHTMLintegration


But I don't think this is the point for now. It seems to me we have to 
think long term and figure out what will be 'bulit-in' capabilities 
for an html browser running in an environment where <x3d> ... </x3d> 
parts are processed without the need for external scripts. I think 
downloading a big set of scripts just to get the thing running should 
not be necessafy. Then the choice becomes what level of 'built-in' 
convenience and automation do we want to provide.

Thanks,
Joe


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160611/5579e111/attachment.html>