You use a one-time token tied to the session data. Add it to every internal link in a single page view then the next request, invalidate that token and create a new one to tag on to every link.
This would get complex when dealing with things like ajax requests, forms, etc., but I believe it could be done.
I suppose that's true in some areas. Mobile devices/costly bandwidth would make a case for it, but I believe that will be less of a problem as time goes on. Moving data always seems to be getting cheaper.
And it's just opinion, but I feel more like "if I want it, I'll ask for it." If something is critical enough that it can't wait until I get around to checking it (probably only a matter of minutes, but that's at my discretion), then there's already a great push system in place I've been using for years: the phone.
Actually there was an option (I called in to the number listed on their website last night) "if you are calling about an outage press 5." Bam, pre-recorded message telling you there was an outage and they had no ETA but expected things to be back up soon. Although I feel your pain, I spent a good few hours triaging with one of our on-call engineers looking into a customer's BES servers only to find it had nothing to do with us.
I believe the affected systems were all of North America (at least from the DNS). I can confirm from work last night that the affected address was srp.us.blackberry.net which is a CNAME for srp.na.blackberry.net.
It was down for quite some time. The (very touchy) customer that reported the problem said it began at about 9pm our NOC time (CDT). There was a brief period where one of the two IPs tied to srp.na.blackberry.net was up for about a half hour, but for the most part they were entirely down until about 5:15am CDT.
/etc/localtime Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 /etc/localtime Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 /etc/localtime Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 /etc/localtime Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0
For those not sure about the parent's post...the command you are looking for is:
[you@yourhost]$ dump -v/etc/localtime | grep 2007
Which on my (correct) system returns:
/etc/localtime Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 /etc/localtime Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 /etc/localtime Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 /etc/localtime Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0
You think Linux distros are going to be supported indefinitely? If you want to do it yourself, fine. But that's only the same as what happens to old Windows OSs. I mean, there are some businesses using MSDOS on 286s. If it works for you, fine. Don't keep up. But don't kid yourself that MS is evil because they don't want to waste money on legacy nonsense.
But that's not the issue here. Sure, you try to install something on an older distro, you might get failures from missing dependencies (compilation or package install), but I can't think of a case where the software says "Nope, you have an older distro therefore I refuse to install."
My $.01 (half price today only - Verizon customer's special only.0001)
Hah...that reminds me of a few years ago...I decided it would be fun to add a hotmail.com zone to local lookups CNAMEd to hotmale.com. I knew instantly when each of my roommates first tried to check their email. "AHHHHHHHHH OH GOD WTF!%$#!"
Slashdot Mirror
Funny, I've seen this before, too.
I'm a lonely loser, you insensitive clod. :(
They haven't banned My liquid drug of choice There's too many hooked And they've got too much voice
Yup. In fact, I was sure I had seen this before, right here on slashdot. I was right.
That sentence made my brain do a little shimmy.
See also: origin of the word sabotage.
I love google.
(256 kbps) * 1 month = 80.2534128 gigabytes
:)
Thanks for the link! I'd mod you up if I had the points.
SONOFA!
I tried to mod your post funny, but missed and hit overrated. I'm posting to make that go away. Oops!
This had some simple answers:
o fing
http://www.rootsecure.net/?p=reports/callerid_spo
I'm sure there's many similar pages out there. Short answer: the real one.
You use a one-time token tied to the session data. Add it to every internal link in a single page view then the next request, invalidate that token and create a new one to tag on to every link.
:)
This would get complex when dealing with things like ajax requests, forms, etc., but I believe it could be done.
Thanks for the idea, GP.
I suppose that's true in some areas. Mobile devices/costly bandwidth would make a case for it, but I believe that will be less of a problem as time goes on. Moving data always seems to be getting cheaper.
And it's just opinion, but I feel more like "if I want it, I'll ask for it." If something is critical enough that it can't wait until I get around to checking it (probably only a matter of minutes, but that's at my discretion), then there's already a great push system in place I've been using for years: the phone.
Actually there was an option (I called in to the number listed on their website last night) "if you are calling about an outage press 5." Bam, pre-recorded message telling you there was an outage and they had no ETA but expected things to be back up soon. Although I feel your pain, I spent a good few hours triaging with one of our on-call engineers looking into a customer's BES servers only to find it had nothing to do with us.
Nothin like having a Severity 1 issue, finding the cause, and being able to say "Hah! Not my problem!" :D
But it uses push technologies! omgz! We all saw how successful that was in the browser world. ...right?
I believe the affected systems were all of North America (at least from the DNS). I can confirm from work last night that the affected address was srp.us.blackberry.net which is a CNAME for srp.na.blackberry.net.
It was down for quite some time. The (very touchy) customer that reported the problem said it began at about 9pm our NOC time (CDT). There was a brief period where one of the two IPs tied to srp.na.blackberry.net was up for about a half hour, but for the most part they were entirely down until about 5:15am CDT.
Speaking of mistakes...that should be zdump not dump. Stupid pastes in addition to stupid linebreaks. :(
/etc/localtime | grep 2007
/etc/localtime Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0
/etc/localtime Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1
/etc/localtime Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1
/etc/localtime Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0
Making the correct post -
For those not sure about the parent's post...the command you are looking for is:
[you@yourhost]$ zdump -v
Which on my (correct) system returns:
Stupid linebreaks.
For those not sure about the parent's post...the command you are looking for is:
/etc/localtime | grep 2007
/etc/localtime Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1
/etc/localtime Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1
/etc/localtime Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0
[you@yourhost]$ dump -v
Which on my (correct) system returns:
/etc/localtime Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0
Stupid linebreaks.
Duh. Just set the evil bit on illegal copies.
You think Linux distros are going to be supported indefinitely? If you want to do it yourself, fine. But that's only the same as what happens to old Windows OSs. I mean, there are some businesses using MSDOS on 286s. If it works for you, fine. Don't keep up. But don't kid yourself that MS is evil because they don't want to waste money on legacy nonsense.
.0001)
But that's not the issue here. Sure, you try to install something on an older distro, you might get failures from missing dependencies (compilation or package install), but I can't think of a case where the software says "Nope, you have an older distro therefore I refuse to install."
My $.01 (half price today only - Verizon customer's special only
Wait wait I'm confused. Which side are you talking about when you say "their/they"?
Hah...that reminds me of a few years ago...I decided it would be fun to add a hotmail.com zone to local lookups CNAMEd to hotmale.com. I knew instantly when each of my roommates first tried to check their email. "AHHHHHHHHH OH GOD WTF!%$#!"
Cathalitic convertors
...Trying to sway pollution from being Protestant?
You think mayo is bad wait till you see a poutine.
But by god, they are tasty.
Oui monsieur coward. J'ai dit cela seulement pour l'humeur.
STOMP STOMP STOMP!
That was the sound of the grammar nazis marching in to take you for using the wrong accént.