Re: Interprocess communication on multi-user machine

2006-07-01 Thread Lawrence D'Oliveiro
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Nick Maclaren) wrote: >In article <[EMAIL PROTECTED]>, >Lawrence D'Oliveiro <[EMAIL PROTECTED]> writes: >|> > >|> >Sockets are often accessed via special files, but are not files. >|> >|> They are files. They are not _regular_ files. > >Yes, I k

Re: Interprocess communication on multi-user machine

2006-06-30 Thread Nick Maclaren
In article <[EMAIL PROTECTED]>, Lawrence D'Oliveiro <[EMAIL PROTECTED]> writes: |> > |> >Sockets are often accessed via special files, but are not files. |> |> They are files. They are not _regular_ files. Sigh. Firstly, look at something like: http://www.opengroup.org/onlinepubs/009695399

Re: Interprocess communication on multi-user machine

2006-06-30 Thread Lawrence D'Oliveiro
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Nick Maclaren) wrote: >In article <[EMAIL PROTECTED]>, >Lawrence D'Oliveiro <[EMAIL PROTECTED]> writes: >|> In article <[EMAIL PROTECTED]>, >|> Michael Butscher <[EMAIL PROTECTED]> wrote: >|> >|> >Normally any user could connect to an open sock

Re: Interprocess communication on multi-user machine

2006-06-30 Thread Nick Maclaren
In article <[EMAIL PROTECTED]>, Michael Butscher <[EMAIL PROTECTED]> writes: |> |> this is not really Python-specific but I need it for Python. |> |> I'm wanting a method for interprocess communication which is OS- |> independent (sockets would be the normal way to go), but which works if |> mu

Re: Interprocess communication on multi-user machine

2006-06-30 Thread Nick Maclaren
In article <[EMAIL PROTECTED]>, Lawrence D'Oliveiro <[EMAIL PROTECTED]> writes: |> In article <[EMAIL PROTECTED]>, |> Michael Butscher <[EMAIL PROTECTED]> wrote: |> |> >Normally any user could connect to an open socket on a machine |> >regardless which user established the socket (the user's pr

Re: Interprocess communication on multi-user machine

2006-06-30 Thread Lawrence D'Oliveiro
In article <[EMAIL PROTECTED]>, Michael Butscher <[EMAIL PROTECTED]> wrote: >Normally any user could connect to an open socket on a machine >regardless which user established the socket (the user's program, to be >precise). That's not true. On *nix systems, a socket is a file, and is subject

Re: Interprocess communication on multi-user machine

2006-06-29 Thread Martin v. Löwis
Michael Butscher wrote: > I'm wanting a method for interprocess communication which is OS- > independent (sockets would be the normal way to go), but which works if > multiple users use the machine at the same time so that one user has no > access to the communication of programs of another user.

Interprocess communication on multi-user machine

2006-06-29 Thread Michael Butscher
Hi, this is not really Python-specific but I need it for Python. I'm wanting a method for interprocess communication which is OS- independent (sockets would be the normal way to go), but which works if multiple users use the machine at the same time so that one user has no access to the communi