On Tue, Mar 25, 2014 at 7:24 AM, Matt Newville
<(E-Mail Removed)> wrote:
> I'm maintaining a python interface to a C library for a distributed
> control system (EPICS, sort of a SCADA system) that does a large
> amount of relatively light-weight network I/O. In order to keep many
> connections open and responsive, and to provide a simple interface,
> the python library keeps a global store of connection state.
>
> This works well for single processes and threads, but not so well for
> multiprocessing, where the global state causes trouble.
>From the sound of things, a single process is probably what you want
here. Is there something you can't handle with one process?
ChrisA
<(E-Mail Removed)> wrote:
> I'm maintaining a python interface to a C library for a distributed
> control system (EPICS, sort of a SCADA system) that does a large
> amount of relatively light-weight network I/O. In order to keep many
> connections open and responsive, and to provide a simple interface,
> the python library keeps a global store of connection state.
>
> This works well for single processes and threads, but not so well for
> multiprocessing, where the global state causes trouble.
>From the sound of things, a single process is probably what you want
here. Is there something you can't handle with one process?
ChrisA
Aucun commentaire:
Enregistrer un commentaire