jaschaephraim / lrserver Goto Github PK

Hi,

first: thanks for this package, I was looking for soemthing like this for a long time! I'm also glad that you didn't integrate the watching yourself but let the users choose how they want to notify clients to reload.

Now to my confusion.. It seems to me that the javascript code tries to create a new websocket all the time. From my experience with websockets, there should only be one request and than an upgrade and further communication is done through frames on that connection.

I see it on both firefox30 and chromium 35.

Firefox also throws an NS_ERROR_NOT_CONNECTED error and points to livereload.js:211 which is here in the javascript.go file.

I'm not sure what's going on and to be clear: Triggering reloads works. It's just that these messages are a bit annoying while debbugging other requests.

Have you seen this before? If not it would be great if you could try it with the small markdown reloader i wrote: livefriday. Could also be that I messed something up during setup.

Thanks.

Hey thanks for creating this :-)

I was wondering if it makes sense in the scope of this project for the livereload server to implement an http.Handler interface?

It would allow less port binding and would be a bit easier to integrate into existing dev servers.

There is no path in New() that can result in an error. Maybe this could be removed?

Thanks for a useful bit of software! What license do you intend to publish this under? I'm guessing that it might be the same as the included livereload Javascript (MIT), but it would be great to make it explicit.