Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-winehq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-winehq
Commits
7e101054
Commit
7e101054
authored
Nov 07, 2001
by
Bill Medland
Committed by
Alexandre Julliard
Nov 07, 2001
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor grammatical corrections.
parent
cf6f12f3
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
6 deletions
+6
-6
architecture.sgml
documentation/architecture.sgml
+6
-6
No files found.
documentation/architecture.sgml
View file @
7e101054
...
...
@@ -55,7 +55,7 @@
Win16 and Win32 applications have different requirements;
for example, Win16 apps expect cooperative multitasking
among themselves, and to exist in the same address space,
while Win32 apps ex
cep
t the complete opposite, i.e.
while Win32 apps ex
pec
t the complete opposite, i.e.
preemptive multitasking, and separate address spaces.
</para>
<para>
...
...
@@ -109,8 +109,8 @@
The wineserver itself is a single and separate process and
does not have its own threading - instead, it is built on
top of a large <function>poll()</function> loop that alerts
the wineserver whenever anything happens, such
that
a client
ha
s sent a command, or a wait condition has
been satisfied.
the wineserver whenever anything happens, such
as
a client
ha
ving sent a command, or a wait condition having
been satisfied.
There is thus no danger of race conditions inside the
wineserver itself - it is often called upon to do operations
that look completely atomic to its clients.
...
...
@@ -118,13 +118,13 @@
<para>
Because the wineserver needs to manage processes, threads,
shared handles, synchronization, and any related issues, all
the client
's
Win32 objects are also managed by the
the client
s'
Win32 objects are also managed by the
wineserver, and the clients must send requests to the
wineserver whenever they need to know any Win32 object
handle's associated Unix file descriptor (in which case the
wineserver duplicates the file descriptor, transmits it to
the client, and leaves to the client to close the duplicate
when
it's done
with it).
the client, and leaves
it
to the client to close the duplicate
when
the client has finished
with it).
</para>
</sect2>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment