Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 18
    On the contrary, I don't see any reason to allow it. Commented Apr 29, 2011 at 13:59
  • 1
    What about a local webapp or an extension? Is it forced to store all its data in a single long html file? Commented Apr 29, 2011 at 15:01
  • 2
    @Karpie I agree with your basic theory, but at the same time disagree with the realistic application. There is a marked difference between academic and applied and, in this case, the suggested workarounds (ie., setting up another server, using security-disabling flags, etc.) seem worse than having an established model where "File in X directory has read permissions on other files in X directory". Perfect? No. Better than kludgy alternatives? Maybe? The example case of "many applications are using HTML help docs" seems a reasonable real-world scenario. Commented May 4, 2011 at 9:20
  • If you want, you can try this over at security.stackexchange.com Commented May 11, 2011 at 19:07
  • 2
    @Karpie - you should explain why rather than just tossing in a throw-away like that. Not everyone understands security implications. Educating about what seems to be a fair question would be nice. Commented May 30, 2011 at 4:36