On Sat, 25 Sep 2010 14:45:29 +0200, Thomas Jollans wrote:
>> 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?
T
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, lo
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 s
On 9/24/2010 12:53 AM, antoine wrote:
Hello,
I would like to create a python server for which the requests are
passed by files on the hard drive instead of a network.
I am currently looking at the SocketServer python module, hoping for
an easy modification.
Is it doable at all?
If yes, how shou
On Friday 24 September 2010, it occurred to antoine to exclaim:
> Hello,
>
> I would like to create a python server for which the requests are
> passed by files on the hard drive instead of a network.
> I am currently looking at the SocketServer python module, hoping for
> an easy modification.
>
Hello,
I would like to create a python server for which the requests are
passed by files on the hard drive instead of a network.
I am currently looking at the SocketServer python module, hoping for
an easy modification.
Is it doable at all?
If yes, how should it be done?
Thanks,
Antoine.
--
htt
