There is a "robustness" principle (frequently noted in RFCs) which I just don't accept. It states "be democratic with what you get, be strict with you give". It's about the code, protocols and interfaces.
Whenever I write something, I prefer using "be pain in the a** with whatever you get". Otherwise a lot of bugs become legal, and a lot of ambiguities appear.
Damn, even HTTP has legitimate bug with chunked output. It should end with \n\n, but it ends with just \n (probably vice versa). Read RFC and check google output with telnet (or any other web site). And FireFox has stepped on this stone with their first version... I even saw request for fixing at RentACoder
Whenever I write something, I prefer using "be pain in the a** with whatever you get". Otherwise a lot of bugs become legal, and a lot of ambiguities appear.
Damn, even HTTP has legitimate bug with chunked output. It should end with \n\n, but it ends with just \n (probably vice versa). Read RFC and check google output with telnet (or any other web site). And FireFox has stepped on this stone with their first version... I even saw request for fixing at RentACoder
