Confirmed users, Bureaucrats and Sysops emeriti
419
edits
JSObject Makeover: Difference between revisions
→JSObjectOps background/notes
| Line 16: | Line 16: | ||
** hence optional JSClass.getObjectOps, "upside-down" new object protocol | ** hence optional JSClass.getObjectOps, "upside-down" new object protocol | ||
* leaky abstraction to let LiveConnect specialize object behavior not hooked via JSClass | * leaky abstraction to let LiveConnect specialize object behavior not hooked via JSClass | ||
* object (scope) locking if JS_THREADSAFE under the JSObjectOps layer | * object (scope) locking if JS_THREADSAFE under the JSObjectOps layer | ||
** generally; again the layering broke down in a few places | |||
** making upper layer lock-free still a worthwhile goal -- atomic object ops, fine grained locking, lock-free objects | ** making upper layer lock-free still a worthwhile goal -- atomic object ops, fine grained locking, lock-free objects | ||
* reluctance to add more ops back in the ABI-matters-for-Netscape (servers as well as client) days | * reluctance to add more ops back in the ABI-matters-for-Netscape (servers as well as client) days | ||