Plugin request: Service Monitor

bentael

hmm .. i don't know if it's possible client-side.. it's not quite working for me.

This thinks the host is always OPEN, ..
http://jsbin.com/OrobAsAV/11/edit?js,console

anyone have an idea?
according to this, it should work, where did I barf?

<baris>

Tried ping({host: 'chi.bdit.ca', port: 9999}, onPing); said it is closed.

Chris

Everything shows open for me as well. Even the example that @baris gave.

I'm not 100% sure you can check open ports via pure javascript except from maybe the client side? I've seen some javascript "port scanners" but I believe they check to see whether or not the client can access that port, not necessarily if it's online.

Chris

@bentael when I was researching it I came across this: http://www.hacksparrow.com/a-port-scanner-in-node-js.html

Not sure if that's helpful or not, or how that works, but yeah.

bentael

@theepiphany yea it's easier server-side (or in NodeJS in this case), but I was trying to have that done on the browser somehow.. to save some bandwidth on the server .. that could get really hairy if you have a lot of users online and a lot servers to ping.

bentael

ill give it another shot tomorrow.. gotta finish up some stuff for my day-job.

Chris

@bentael Makes sense. Would probably be better to globally cache/save the status' and check them after a certain interval or something? Not sure.

bentael

Still not successful client-side -- need server hAlp

julian

Checked your jsBin from earlier, 9999 says it is closed again

bentael

@julian yea but i try some fake url it would say OPEN
http://jsbin.com/OrobAsAV/16/edit?js,console
do you think that's because the fake url doesn't even resolve, so the onerror would trigger immediately?

so I would need another way to resolve?

julian

That could be worth a shot. Try overriding onerror to see if it is being run instead of onload?