Date: Mon, 25 Mar 1996 18:34:12 +1100 (EST) From: John Birrell <cimaxp1!jb@melb.werple.net.au> To: atrad.adelaide.edu.au!msmith@melb.werple.net.au (Michael Smith) Cc: atrad.adelaide.edu.au!cimaxp1!jb@melb.werple.net.au, freebsd.org!doc@melb.werple.net.au, freebsd.org!julian@melb.werple.net.au, cimlogic.com.au!jb@melb.werple.net.au Subject: Re: POSIX thread docs Message-ID: <199603250734.SAA08730@melb.werple.net.au> In-Reply-To: <199603250704.RAA28981@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Mar 25, 96 05:34:26 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > Thanks for the work! Now I have to find something to use threading for 8) Ahh, that's easy. Should go well with __ > | > -- | > ]] Mike Smith, Software Engineer | msmith@atrad.adelaide.edu.au [[ > ]] Genesis Software | genesis@atrad.adelaide.edu.au [[ > ]] High-speed data acquisition and \_| (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control / (ph/fax) +61-8-267-3039 [[ > ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ > We provide network access to devices with threaded programs. Take a PLC interface like Allen-Bradley KF2. Connect that box via a serial port to a threaded server program that has the initial thread waiting for clients to connect via sockets. Leave a thread listening to the serial port. For each socket connection, create a client thread. Works _much_ faster than forking or trying to handle multiple clients in a single thread. And all without stressing the OS. -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603250734.SAA08730>