Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The current fix to the problem is to append .nyud.net:8090 to any requests.

    One possible flaw in your idea (which I like) is that my browser may be privy to pages I don't want others to access. Each user's experience on a site may be customized in ways that would render P2P sharing of pages either useless or insecure. Would you want your browser to help distribute the load for use perl when the cached contents are what use perl looks like when you log in? How about for your online bank? ;)

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • Yes, this is only for basic "page for the world to see" situation. A bank would not use the extended protocol and would never refer a request on to an earlier viewer.

      Someone could not use your browser to get access to a site that you are privy too, but they are not - they would not be passed on to you by the original site. (However, the original site will have to check fo valid users and only pass on requests that it would have actually honoured, which is probably expensive enough to not bother with this protocol for security restricted sites.)