Re:If your code accepts URIs as input, filter out “file://”
by mootothemax on Monday September 12, 2016 @07:38AM
(#12478825)
Yeah, apologies, I was being pretty petty.
My hopefully-better-expressed point is that it's easy to interpret the robustness principle in different ways, some of which lead to better code, and some of which... don't.
Re:If your code accepts URIs as input, filter out “file://”
by artursapek on Monday September 12, 2016 @12:40PM
(#12481205)
No worries. I think the philosophy is rooted in the fact that you can't control what other parties will send you; you can only control what you send in response. So that's the main thing to keep in mind.
It's sort of like the good life advice you hear occasionally: you can't control other peoples' actions; only your own. Emotional maturity, etc.
Re:If your code accepts URIs as input, filter out “file://”
by toomanybeersies on Monday September 12, 2016 @10:07AM
(#12479758)
Isn't that missing the point of the robustness principle, which is more related to say, networking, and accepting things that aren't strictly to RFC spec, but when sending things, you match the spec to the letter?
Re:If your code accepts URIs as input, filter out “file://”
by artursapek on Monday September 12, 2016 @10:11AM
(#12479788)
I've found it useful in software design in general.
> Be conservative in what you do
However, you only handle specific schemes and ignore the rest.