> > > This would be possible, but requires a different session strategy. > > The Pil system forks a child process for each session, which then uses > its own private port to listen for further client connections. > > ...
> I believe that the current solution is very good (for several reasons we > discussed here and in IRC. > > Thanks! I appreciate the explanation. I haven't dug into the code enough, but I'll see if I can at least restrict the ports used for administration sessions /Lindsay
