You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should rewrite the strands_webserver to remove the rather silly serving of .js files etc, and also to manage displays in a more sensible way. Further, in order to be able to use web.py for GUI, allowing easy server-side mongodb access .
The webserver should be replaced with a we.py server. Different paths should be used to explicity manage display numbers for multiple displays. Content should be provided to the webserver using a plugin system.
The text was updated successfully, but these errors were encountered:
In #75 we have discussed that indeed we also need the ability to serve files that are in other (dynamically chosen) places. @cdondrup has the use case to stream media files via the webserver. This is similar to serving javascript and css files from another package (here: strands_webtool). So, we need to be able to serve files that are not all under one root dir. Different dirs should be served as different URLs, which clearly calls for a web.py solution. Indeed, the AAF control GUI server uses a similar apporach to serve its javascript files from strands_webtools that could be adopted.
We should rewrite the
strands_webserver
to remove the rather silly serving of.js
files etc, and also to manage displays in a more sensible way. Further, in order to be able to use web.py for GUI, allowing easy server-side mongodb access .The webserver should be replaced with a we.py server. Different paths should be used to explicity manage display numbers for multiple displays. Content should be provided to the webserver using a plugin system.
The text was updated successfully, but these errors were encountered: