Plugin request: Service Monitor
-
Ha! Oh Twilio, I've used their service before. One of the best APIs I've used.
Would be nice to have a plugin that'll text you when you get notified... though I imagine it could get a little hairy if you don't throttle well. (e.g. 4 texts all related to one topic (chuckle))
-
@julian said:
Ha! Oh Twilio, I've used their service before. One of the best APIs I've used.
Would be nice to have a plugin that'll text you when you get notified... though I imagine it could get a little hairy if you don't throttle well. (e.g. 4 texts all related to one topic (chuckle))
Twilio is easily one of the best API's I've ever seen. It's so easy it's like the fisherprice of API's, haha.
Yeah I was thinking of a way you could ensure you're only notified when you want to be, or select specific type only like mentions only or messages only, something like that.
-
@theepiphany
can you provide a couple of hosts w/ ports to test ping.Trying to see if I can ping client-side.
-
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,consoleanyone have an idea?
according to this, it should work, where did I barf? -
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.
-
@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.
-
ill give it another shot tomorrow.. gotta finish up some stuff for my day-job.
-
Still not successful client-side -- need server hAlp
-
@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?