T.R | Title | User | Personal Name | Date | Lines |
---|
1607.1 | | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Mon Oct 07 1991 08:57 | 5 |
| Isabelle,
What is meant by "in the Software organization"? Are you
refering to management (people) or the product (modules)?
|
1607.2 | | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Mon Oct 07 1991 09:45 | 5 |
| Quite general answer.
No.
|
1607.3 | I mean... | PADIS::PERIE | | Mon Oct 07 1991 14:34 | 5 |
|
What I mean by software organization is for example how is the thread
mecanism implemented , process activated per each DECmcc module...
Isabelle.
|
1607.4 | | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Mon Oct 07 1991 17:26 | 5 |
| Threads are the same - all in one process.
Management modules are different. All in one process in VMS. Once
process per MM in Ultrix.
|
1607.5 | ultrix process model | TOOK::CALLANDER | MCC = My Constant Companion | Wed Oct 23 1991 19:17 | 5 |
| Jim, Isn't that one process per MM per user. So if one user logs into
the same account 5 times and runs mcc, there will never be more than
one process per MM that they are using. But if 5 users log into 5
different account, each of them will have their own set of MCC MM
processes.
|
1607.6 | and for developpers , and users? | PADIS::PERIE | | Wed Nov 20 1991 11:05 | 6 |
| Thanks a lot for your answers.
What about (differences Ultrix,VMS) from the developper point of view ?
And from the user point of view?
Thanks.
Isabelle.
|
1607.7 | new dev toolkit documentation includes ultrix info | TOOK::CALLANDER | MCC = My Constant Companion | Wed Jan 08 1992 10:12 | 12 |
|
The new developers toolkit documentation has been completely reworked
so as to explain both environments, and to describe development in
terms of platform independence.
The level of OS knowledge needed by a developer will be dependent upon
the type of function to be provided. As much as possible we have put
kernel routines around system services so as to make them "generic"
from the developers point of view. The close you stick to MCC routines
and standard C calls the more portable your code.
|