Effective COM : (Record no. 3211)

MARC details
000 -LEADER
fixed length control field 02737cam a2200277 a 4500
001 - CONTROL NUMBER
control field 3090382
003 - CONTROL NUMBER IDENTIFIER
control field OSt
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20231019165940.0
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 980916s1999 maua 001 0 eng
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 0201379686
040 ## - CATALOGING SOURCE
Original cataloging agency BUL
Transcribing agency BUL
Modifying agency BUL
Language of cataloging Eng
Description conventions rda
082 00 - DEWEY DECIMAL CLASSIFICATION NUMBER
Edition number 22
Classification number 005.276
Item number EFF
245 00 - TITLE STATEMENT
Title Effective COM :
Remainder of title 50 ways to improve your COM and MTS-based applications /
Statement of responsibility, etc. Don Box . . . [et al.].
260 ## - PUBLICATION, DISTRIBUTION, ETC.
Place of publication, distribution, etc. Reading, Mass :
Name of publisher, distributor, etc. Addison-Wesley,
Date of publication, distribution, etc. c1999.
300 ## - PHYSICAL DESCRIPTION
Extent xv, 222 p. :
Other physical details ill. ;
Dimensions 24 cm.
440 #0 - SERIES STATEMENT/ADDED ENTRY--TITLE
Title Addison-Wesley object technology series
500 ## - GENERAL NOTE
General note TABLE OF CONTENTS<br/><br/>Shifting from C++ to COM<br/>1. Define your Interface Before you Define Your Classes (and do it in IDL).<br/>2. Design with Distribution in Mind<br/>3. Objects should not Have their Own Interface<br/>4. Beware the COM Singleton<br/>5. Don't Allow C++ Exception to Cross Method Boundaries<br/><br/>Interfaces<br/>6. Interfaces are Syntax and Loose Semantics. Both are Immutable<br/>7. Avoid E_NOTIMPL.<br/>8. Prefer Typed Data to Opeque Data<br/>9. Avoid Connection Points<br/>10. Don't Provide More than One Implementation of the same Interface on a Single Object<br/>Etc.<br/><br/>Implementation<br/>18. Code Defensively<br/>19. Always Initialize [ out ] Parameters<br/>20. Don't Use Interface Pointers that Have not Been AddRef ' ed<br/>21. Use Static_Cast when Bridging Between the C++ Type System and the COM Type System<br/>22. Smart Interface Pointers add at least as Much Complexity as they Remove<br/>Etc. <br/><br/>Apartments<br/>29. Don't Access Raw Interface Pointers Across Apartment Boundaries<br/>30. Whe Passing an Interface Pointer Between One MTA Thread and Another, Use AddRef .<br/>31. User-Interface Threads and Objects Must Run in Single-Threaded Apartments (STAs).<br/>32. Avoid Creating Threads from an in-Process Server<br/>33. Beware the Free-Threaded Marshaler (FTM).<br/>Etc.<br/><br/>Security<br/>38. CoInitializeSecurity is Your Friend. Learn it, Love it, Call it.<br/>39. Avoid AS-Activator Activation<br/>40. Avoid Impersonation<br/>41. Use Fine-Grained Authentication<br/>42. Use Fine-Grained Access Control<br/><br/>Transactions<br/>43. Keep Transactions as Short as Possible<br/>44. Always Use SafeRef When Handing out Pointers to your Own Object<br/>45. Don't Share Object References Across Activity Boundaries<br/>46. Beware of Exposing Object References from the Middle of a Transaction Hierarchy<br/>47. Beware of Committing a Transaction Implicitly<br/>Etc.<br/><br/><br/><br/>
504 ## - BIBLIOGRAPHY, ETC. NOTE
Bibliography, etc. note Includes : index: p. 205-222<br/><br/><br/>
630 00 - SUBJECT ADDED ENTRY--UNIFORM TITLE
Uniform title Microsoft Transaction server.
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Application software
General subdivision Development.
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Object-oriented programming (Computer science)
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element COM (Computer architecture)
700 1# - ADDED ENTRY--PERSONAL NAME
Personal name Box, Don.
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Source of classification or shelving scheme Dewey Decimal Classification
Koha item type Book Open Access
Classification part 005.276
Item part 1
Call number prefix EFF
Call number suffix 005.276 EFF
Holdings
Withdrawn status Lost status Source of classification or shelving scheme Damaged status Not for loan Home library Current library Date acquired Source of acquisition Inventory number Total Checkouts Full call number Barcode Date last seen Copy number Price effective from Koha item type
    Dewey Decimal Classification     Engineering Library Engineering Library 04/28/2021 Donation 0019528   005.276 EFF 1 BUML23101123 04/28/2021 1 04/28/2021 Book Open Access