You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ernest Allen (JIRA)" <ji...@apache.org> on 2016/01/04 16:28:39 UTC
[jira] [Resolved] (DISPATCH-151) Add ability to run websockets/tcp
proxy and http file server
[ https://issues.apache.org/jira/browse/DISPATCH-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ernest Allen resolved DISPATCH-151.
-----------------------------------
Resolution: Implemented
Fix Version/s: 0.5
Added a ConsoleEntity agent. The config file can now contain a Console section to automatically start a console when the routers starts.
> Add ability to run websockets/tcp proxy and http file server
> ------------------------------------------------------------
>
> Key: DISPATCH-151
> URL: https://issues.apache.org/jira/browse/DISPATCH-151
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Management Agent
> Affects Versions: 0.5
> Reporter: Ernest Allen
> Assignee: Ernest Allen
> Fix For: 0.5
>
>
> Currently, if you want to connect to a router directly from a web page using the proton javascript bindings, you need to run a proxy server.
> Also, if you want to serve the static html/js/css files for the dispatch console, you need to start a web server like tomcat.
> We can integrate this functionality into the router by:
> - creating a stand-alone "qdproxy" python program that serves both as a websocket/tcp proxy and a file server
> - modify the schema to configure qdproxy
> - modify the router startup/configuration to run the proxy when the router starts
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org