SocketServer: replace network by hard drive

Thomas Jollans thomas at jollybox.de
Sat Sep 25 08:45:29 EDT 2010


On Saturday 25 September 2010, it occurred to Nobody to exclaim:
> On Fri, 24 Sep 2010 19:28:45 +0200, Thomas Jollans wrote:
> > If you're using UNIX, and you don't actually need the stream to be
> > passed via the hard drive (why would you?), but for some reason want to
> > use the file system, look info UNIX/local sockets. But, really, I'm
> > guessing that local TCP sockets (our old friend 127.0.0.1/8) will work
> > just as well for whatever you're doing (though I may be mistaken), are
> > portable to non-UNIX system, and won't be any slower than UNIX domain
> > sockets on most, if not all, systems.
> 
> The problem with using the loopback interface is that it's still
> "network access", which can run into all kinds of issues with security
> policies, firewalls, etc.

What kind of crappy firewall blocks loopback traffic? Really?



More information about the Python-list mailing list