[ https://issues.jboss.org/browse/JBIDE-13950?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-13950 at 4/26/13 4:42 AM: ---------------------------------------------------------------- After discussing about it with Max, here are the way we'll implement the support for Server Mode: - At minimum, the LiveReload server accepts connection on the 35729 port (configurable). - The file:// scheme support remains unchanged: users can access local files and use the manually installed browser extension to connect to the LiveReload server and see updates as they save HTML/CSS/JS/Image files in their editors. - The LiveReload server should listen to other Servers events, in particular: Start/Stop/Restart on other servers. As soon as an App Server (JBoss AS, Tomcat, etc.) starts, the LiveReload server accept incoming requests on the 35729 port (or anything else configured by the user), or open a socket on a high range port if reusing the same socket is not possible.Then, the LiveReload server should activate the "proxy" mode to forward all incoming requests to the app server. Returned HTML page should be modified on-the-fly to include the {noformat}<script src="http://localhost/livereload.js"></script>{noformat} element at the bottom of the page. - To access this proxy, a new "Show In>Web browser with LiveReload" action should be available on the Server and the Server Modules in the Servers View. - When the app server publishes some content, the Browser (restrict to those that are connected to this app server only) would be notified by the LiveReload server that some changes occurred. - If the user connects to the App Server without passing through the proxy mentionned above, he would have to enable the LiveReload support using his browser extension (as in case #2). If everything stated above works as expected, a single LiveReload server should cover all use-cases \o/ was (Author: xcoulon): After discussing about it with Max, here are the way we'll implement the support for Server Mode: - At minimum, the LiveReload server accepts connection on the 35729 port (configurable). - The file:// scheme support remains unchanged: users can access local files and use the manually installed browser extension to connect to the LiveReload server and see updates as they save HTML/CSS/JS/Image files in their editors. - The LiveReload server should listen to other Servers events, in particular: Start/Stop/Restart on other servers. As soon as an App Server (JBoss AS, Tomcat, etc.) starts, the LiveReload server should open a socket (on a high range port) and activate the "proxy" mode to forward all incoming requests to the app server. Returned HTML page should be modified on-the-fly to include the {noformat}<script src="http://localhost/livereload.js"></script>{noformat} element at the bottom of the page. - To access this proxy, a new "Show In>Web browser with LiveReload" action should be available on the Server and the Server Modules in the Servers View. - When the app server publishes some content, the Browser (restrict to those that are connected to this app server only) would be notified by the LiveReload server that some changes occurred. - If the user connects to the App Server without passing through the proxy mentionned above, he would have to enable the LiveReload support using his browser extension (as in case #2). If everything stated above works as expected, a single LiveReload server should cover all use-cases \o/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira