Based on the configuration and the mechanism of multitasking in windowsnt , the software concurrent program is designed , including three procedures and multithreading , taking mutex semaphores as synchronization objects , to accomplish concertedly the simulation support software ' s tasks in terms of sharing one and the same real - time simulation database 然后根据实时仿真支撑软件的结构,利用windowsnt的多任务机制,以目前最流行的面向对象的程序设计思想,进行了windowsnt下并发程序的设计,采用三个进程和多个线程,以互斥信号量为同步对象,在共享同一个实时仿真数据库的前提下,协调完成仿真支撑软件的各项任务。
This design failing was compounded by at least two failings of execution - it was run only on a single - processor system an unusual environment for a highly concurrent program , and whose synchronization performance may well differ substantially from multiprocessor systems , and only on a single platform 除了设计上的失败,在执行方面至少也有两大败笔它只在单处理器系统(对于高并发性程序来说,这是一种不寻常的系统,其同步性能与在多处理器系统上可能有本质上的差别)上,并且只在一个平台上执行。
What s more , simple concurrent programming has been available on essentially all unix hosts since at least 1988 , which is when ksh standardized its " co - processes . " if you save the ksh source in listing 1 , below , as ex1 . ksh and then run it , you ll see a " countdown " - " ten , nine , eight , etc . " - display , then the result of the ksh subprocess : " all done . " in practice , you might use something like this for a long - running chemical calculation or database retrieval : launch the operation as a subprocess , but keep users informed about what s going on or how much time is left before completion 此外,至少自1988年以来,基本上已经在所有unix主机上实现了简单的并发编程,在1988年这一年ksh对其“协同进程( co - process ) ”进行了标准化。如果您将下面清单1中的ksh源代码保存为ex1 . ksh ,然后运行它,您会看到“倒计时”显示: “十、九、八,等等” ,然后看到ksh子进程的结果: “ all done ” 。实际运用中,您可能会对长期运行的化学计算或数据库检索使用类似这样的操作:启动操作作为子进程,但是让用户始终知道操作的进展或完成之前还剩多少时间。