Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strands_webserver rewrite #59

Open
cburbridge opened this issue Feb 10, 2015 · 3 comments
Open

strands_webserver rewrite #59

cburbridge opened this issue Feb 10, 2015 · 3 comments

Comments

@cburbridge
Copy link
Member

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.

@hawesie
Copy link
Member

hawesie commented Feb 10, 2015

Agreed!

@hawesie
Copy link
Member

hawesie commented Feb 10, 2015

As no-one else has any jobs for me this week, I can make a start on it.

@marc-hanheide
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants