File: README

package info (click to toggle)
ace 6.0.3%2Bdfsg-0.1
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 49,368 kB
  • sloc: cpp: 341,826; perl: 30,850; ansic: 20,952; makefile: 10,144; sh: 4,744; python: 828; exp: 787; yacc: 511; xml: 330; lex: 158; lisp: 116; csh: 48; tcl: 5
file content (36 lines) | stat: -rw-r--r-- 1,175 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
Presently, this directory contains only one example application for
SPIPEs.  The test source code is contained in SPIPE-acceptor.h and
SPIPE-connector.h.

The SPIPE-acceptor example illustrates how named pipes are used on NT.
Once the server establishes a connection to a single client, it spawns
a thread pool to handle incoming requests via the proactor event loop.
That is, a separate thread from the pool is used to process each
message sent by a client.  The size of the thread pool can be
specified by command-line arguments.  This example leverages the
queueing performed by the NT kernel to trivially implement a thread
pool architecture.

test_spipe_acceptor has the following command-line arguments:

test_spipe_acceptor -t <threads>

<threads> specifies the size of the thread-pool running in the
proactor event loop.

Here's how to run the tests:

% test_spipe_acceptor -t 1000000
starting up daemon test_sock_acceptor
Opening acepipe
hello

% test_spipe_connector
starting up daemon test_sock_connector
Opening acepipe
activating 5
 
please enter input..: hello

There are a number of other options that you can provide.  Please see
the source code for details.