IWETHEY v. 0.3.0 | TODO
1,095 registered users | 1 active user | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Just to be clear

I'm not arguing that Google shouldn't fix this; obviously it's a serious problem. I'm just saying, a lot of the problem wouldn't exist if people would follow the damn RFC.

\r\n\r\n

Also, a logout link doesn't, IMO, cause a problem. It changes state, so yes it's non-idempotent, but it doesn't take a destructive action.

--\r\nYou cooin' with my bird?
\r\n[link|http://www.shtuff.us/|shtuff]
New RFCs are clear on SHOULD vs. MUST
Turning SHOULD into MUST in many an RFC would be a Very Good Thing, albeit too late to contain the damage.
New Yes they are.

They're also quite clear that if you do something the RFC says you SHOULD NOT do, then you might well run into nasty problems, and that the SHOULD NOT is used with the best of intentions to prevent this happening to you.

--\r\nYou cooin' with my bird?
\r\n[link|http://www.shtuff.us/|shtuff]
     Google Web Accelerator is a Bad Thing - (ben_tilly) - (13)
         Thanks, good to know. - (admin)
         Nice to see someone understands HTTP - (ubernostrum) - (10)
             Maybe, but it will mess up our user metrics - (tuberculosis) - (1)
                 I doubt this will be a problem for long. - (ubernostrum)
             I beg to disagree - (ben_tilly) - (7)
                 It's a SHOULD NOT - (ubernostrum) - (6)
                     Coming from them it would be hypocrisy - (ben_tilly) - (5)
                         Two things: - (ubernostrum) - (4)
                             Colour me unconvinced - (ben_tilly) - (3)
                                 Just to be clear - (ubernostrum) - (2)
                                     RFCs are clear on SHOULD vs. MUST - (dws) - (1)
                                         Yes they are. - (ubernostrum)
         Shouldn't be a problem from our apps... - (ChrisR)

A cheery thought that I shall leave you with...
54 ms