Question about current downtime/UDP
Posted: Wed Nov 23, 2005 8:34 am
Do we know what caused this down time?
here's my situation, and it'll sound stupid but let me go.
I was developing an app (well testing the UDP because this is my first solo socket Program, and first UDP program) The day before the downtime I sent the messages, and thought I was not getting responses, however it just wasn't displaying the responses. Now I wasn't hammering the server mind you, I sent a simple message and was waiting up to a minute for a response that didn't come. Shouldn't be a big deal for either of.
However the day later I reexamined my code, and noticed the flaw, fixed it, updated my password and sent it again (using a raw password makes me a bit iffy as well, but that's another discussion) sent the message (an AUTH to make sure I could log in) work up again. and got this response
"505 ILLEGAL INPUT OR ACCESS DENIED"
for which I celebrated my first verified UDP connection, but the message confused me, but I figured I fucked up the order of imputs or something. So I went to check out the website, (about 2 minutes at least had passed a log I have says 5:11PM eastern time was when i got my response but it's definatly unreliable)
Well the story continues that the website was down after the time I wasted, and now I'm sorta feeling like the kid who was playing with the toys and left them out and the father came home and broke his back on something (possibly the toy possibly just fell down the stairs in a drunken stupor) But I just wanted to check what was the chances of us finding out the reason for this down time. Or the possiblity that this could have had something to do with it?
And appologizes about the long winded post it's just hard to explain what I'm feeling. I figure that the UDP should be able to stand this error, but I've also been told by numerous sources the fragility of UDP and so on.. So I'm still a bit worried, if anyone can see a mistake here or in the following line or if this is the problem on the server caused my error I'd like to know so I don't keep thinking I did this.
"AUTH user=kinglink&pass=<clean_plain_text_password_withheld> &protover=0.02c&client=kinglink&clientver=0.0"
here's my situation, and it'll sound stupid but let me go.
I was developing an app (well testing the UDP because this is my first solo socket Program, and first UDP program) The day before the downtime I sent the messages, and thought I was not getting responses, however it just wasn't displaying the responses. Now I wasn't hammering the server mind you, I sent a simple message and was waiting up to a minute for a response that didn't come. Shouldn't be a big deal for either of.
However the day later I reexamined my code, and noticed the flaw, fixed it, updated my password and sent it again (using a raw password makes me a bit iffy as well, but that's another discussion) sent the message (an AUTH to make sure I could log in) work up again. and got this response
"505 ILLEGAL INPUT OR ACCESS DENIED"
for which I celebrated my first verified UDP connection, but the message confused me, but I figured I fucked up the order of imputs or something. So I went to check out the website, (about 2 minutes at least had passed a log I have says 5:11PM eastern time was when i got my response but it's definatly unreliable)
Well the story continues that the website was down after the time I wasted, and now I'm sorta feeling like the kid who was playing with the toys and left them out and the father came home and broke his back on something (possibly the toy possibly just fell down the stairs in a drunken stupor) But I just wanted to check what was the chances of us finding out the reason for this down time. Or the possiblity that this could have had something to do with it?
And appologizes about the long winded post it's just hard to explain what I'm feeling. I figure that the UDP should be able to stand this error, but I've also been told by numerous sources the fragility of UDP and so on.. So I'm still a bit worried, if anyone can see a mistake here or in the following line or if this is the problem on the server caused my error I'd like to know so I don't keep thinking I did this.
"AUTH user=kinglink&pass=<clean_plain_text_password_withheld> &protover=0.02c&client=kinglink&clientver=0.0"