home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!ukma!netsys!decwrl!pa.dec.com!e2big.mko.dec.com!star.enet.dec.com!stonecypher
- From: stonecypher@star.enet.dec.com ()
- Subject: Naming Convention for Named Objects?
- Message-ID: <1992Nov13.184516.10985@e2big.mko.dec.com>
- Lines: 31
- Sender: usenet@e2big.mko.dec.com (Mr. USENET)
- Reply-To: stonecypher@star.enet.dec.com ()
- Organization: Digital Equipment Corporation
- Date: Fri, 13 Nov 1992 18:45:16 GMT
-
-
- Has Microsoft published a spec detailing naming conventions for named
- objects? Names for named objects are system-global, so it is possible that
- two different applications will (unintentionally) conflict, choosing the
- same name for an object.
-
- A naming convention would act as a gentleman's agreement across application
- developers about global object names. I realize that a naming convention
- doesn't prevent malicious action on the part of a developer, but it is a
- necessary step for prevention of unintended name conflicts.
-
- I imagine Microsoft intends developers to embed the organization and
- application names in the object's name. For example, imagine that
- Microsoft App1 and Digital App2 both want to create a named pipe:
-
- \MICROSOFT\APPLICATION\APP1\MYNAMEDPIPE
- \DIGITALEQUIPMENT\APPLICATION\APP2\MYNAMEDPIPE
-
- This type of naming convention would prevent unintended collisions. Is
- there an official Microsoft spec detailing a naming convention?
-
- I'm not asking about object domains -- just plain objects, like a named pipe
- which is used as a generic service request channel, for server/client
- session startup. Nor am I asking about access tokens -- I realize they are
- important for some classes of objects.
-
- Thanks!
-
- -----------------------------------------------------------------------------
- Tom Stonecypher, Digital Equipment Corporation, stonecypher@star.enet.dec.com
- -----------------------------------------------------------------------------
-