[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-333) NeedInfo: How does LiveReload work?

[Michelle Murray (JIRA)]

    [ https://issues.jboss.org/browse/TOOLSDOC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776214#comment-12776214 ] 

Michelle Murray commented on TOOLSDOC-333:
------------------------------------------

Another question:
* In Servers tab, user starts LiveReload server. User double-clicks LiveReload server and opens configuration info in new tab. User selects 'Enable Proxy Server' check box and perhaps changes some other settings. User presses Ctrl+S to save the changes. Does the user then need to stop and restart the LiveReload server for changes to take effect or does the server stop&start automatically? Or is stop&start not necessary?
                
> NeedInfo: How does LiveReload work?
> -----------------------------------
>
>                 Key: TOOLSDOC-333
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-333
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: User Guide
>    Affects Versions: 4.1.0
>            Reporter: Michelle Murray
>            Assignee: Xavier Coulon
>
> I am trying to document LiveReload Tools (integration of LiveReload in JBDS) and I have some questions about how it works.
> Users need a LiveReload server within the IDE and the LiveReload browser extension installed in Chrome or Firefox. Why are both needed? How is the work process distributed between the two? Which is responsible for which tasks?
> I ask because I could imagine the browser extension just looking for changes in file time stamps and consequently reloading pages. It clearly isn't as simple as that but I don't see how the LiveReload server fits in.
> Just read an email from Max to Burr, which separated functions into server-side and client-side. So does LiveReload work something like this: "The LiveReload server handles the server-side of the LiveReload action, such as sending request to refresh web pages. The browser extension handles the client-side of the LiveReload action, such as refreshing pages."

--
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