|
| |
| | SGI - Developer Central Open Source OpenGL® Sample Implementation |
 | | The SGI Free Software License B, as applied to the OpenGL Sample Implementation, is a license to the sample implementation, a reference implementation of the OpenGL, GLU, and GLX APIs, as well as the basis for almost all vendor-supported OpenGL hardware drivers. | | | The Sample Implementation is a reference implementation of the OpenGL, GLU, and GLX APIs, and also serves as the basis for almost all vendor-supported OpenGL hardware drivers in existence today. | | | Releasing the Sample Implementation is part of SGI's commitment to and support for OpenGL, and will help it move to new platforms as the computing industry and 3D graphics hardware evolve. |
|
http://oss.sgi.com/projects/ogl-sample/faq.html
(2609 words)
|
|
| |
| | Java 2 Platform SE v1.3.1: Interface Object |
| | If it is a local object (that is, running in the same VM as the client), invocations may be directly serviced by the object instance, and the object reference could point to the actual instance of the object implementation class. | | | The server object implementation is not involved in creating the duplicate, and the implementation cannot distinguish whether the original object reference or a duplicate was used to make a request. | | | If a CORBA object is a remote object (that is, running in a different VM from the client), the object reference points to a stub (proxy) which uses the ORB machinery to make a remote invocation on the server where the object implementation resides. |
|
http://java.sun.com/j2se/1.3/docs/api/org/omg/CORBA/Object.html
(2609 words)
|
|
| |
| | MIDP for OS X |
| | Please note that the CLDC and MIDP reference implementation, on which the ports for Mac OS X are based, are covered by the Sun Community Source License agreement, which we encourage you to review. | | | Until Sun gets around to releasing their MIDP 2.0 reference implementation for OS X, the one and only MIDP 2.0 solution for the Mac is mpowerplayer. | | | This package is a Darwin/OSX port of the Mobile Information Device Profile (MIDP) Reference Implementation v1.0.3. |
|
http://mpowers.net/midp-osx
(368 words)
|
|
| |
| | The Old Joel on Software Forum - Smart Pointers in Heron |
| | Reference Counting is why Greenspun's 10th law is that "every large C program contains a *bad* implementation of at least 50% of Common Lisp" instead of just "every large C program contains an implementation of at least 50% of Common Lisp". | | | Counting weak references is a CPU load that itself has the distinct possibility of causing performance problems in complex systems -- hence the release build could ship with it weak reference counting turned off. | | | Furthermore, you could make a really awesome debug-weak-reference class that would track the individual references so that you'd know exactly where the problem is. Heck, you can even have a "Default" reference handler and also a way to specify which reference handler is to be used. |
|
http://discuss.fogcreek.com/joelonsoftware?cmd=show&ixPost=167414
(1846 words)
|
|
| |
| | Xerces2 Java Parser Readme |
| | The Apache Xerces2 parser is the reference implementation of XNI but other parser components, configurations, and parsers can be written using the Xerces Native Interface. | | | For complete design and implementation documents, refer to the XNI Manual. | | | Xerces2 also provides a complete implementation of the Document Object Model Level 3 Core and Load/Save W3C Recommendations and provides a complete implementation of the XML Inclusions (XInclude) W3C Recommendation. |
|
http://xerces.apache.org/xerces2-j
(410 words)
|
|
| |
| | Blog Entry: On Reference Objects (java.lang.ref) |
| | Reference queues can be assigned to reference objects at their creation time, and depending on the implementation, each reference will wind up in the queue after the event that defines that reference type has occured. | | | The exact rules for when a soft reference is reclaimed are implementation dependent, but the academic explanation is that an out of memory error will never occur while there are still soft references to be reclaimed. | | | Phantom references are a special type of reference that are simply a way to track the garbage collection of an object. |
|
http://www.coffee-bytes.com/servlet/ShowEntryForId?id=107
(410 words)
|
|
| |
| | Implementing Reference Counting |
| | A common implementation approach for most objects is to have only one implementation of these methods (along with QueryInterface), which is shared between all interfaces, and therefore a reference count that applies to the entire object. | | | Reference counting requires work on the part of both the implementor of a class and the clients who use objects of that class. | | | An example of how reference counts are strictly per-interface-pointer occurs when a client calls QueryInterface on the first pointer for either a new interface or the same interface. |
|
http://msdn.microsoft.com/library/en-us/com/html/d4fd98c9-afa4-4c5c-a3c9-44d34881cbdb.asp?frame=true
(419 words)
|
|
| |
| | Citations: Process decomposition through locality of reference - Rogers, Pingali (ResearchIndex) |
| | Rogers, K. Pingali, "Process decomposition through locality of reference," ACM Sigplan '89 Conference on Programming Language Design and Implementation, June 1989, Portland Oregon. | | | Rogers and K. Pingali, "Process decomposition through locality of reference", in Proceedings of ACM SIGPLAN International Conference on Program Language Design and Implementation, June 1989. | | | Rogers and K. Pingali, "Process decomposition through locality of reference," in Proceedings of the SIGPLAN '89 Conference on Programming Language Design and Implementation, (Portland, OR), June 1989. |
|
http://citeseer.ist.psu.edu/context/12958/0
(2625 words)
|
|
| |
| | issue8839.txt |
| | Whether there are dangling references or not in the DomainManager, is a distributed object computing problem that needs to be dealt with regardless (for example if the DeviceManager and it.s associated devices go down and never come back up) and should be dealt with on the client side as implementation detail. | | | Whether the identifier or the reference is used, is implementation detail on how to determine the duplication, the what is the behavior that should be specified for system design consistency. | | | I realize that not all 'dangling' reference issues are specified but that does not mean we should ignore cases like this when there is a specific question on an interface behavior. |
|
http://www.omg.org/issues/issue8839.txt
(19861 words)
|
|
| |
| | Rijndael in JavaScript |
| | As a reference implementation, it is unoptimized, meaning that it is not suitable for large amounts of data (say, more than several kilobytes) or speed-critical applications. | | | If you need to interoperate with other implementations (for example, a Perl CGI), you will want to take care that padding is added and stripped in a consistent manner, or switch one of many standard padding schemes. | | | The only other Rijndael implementation I'm aware of in JavaScript is from DevGuru.com, but costs $300. |
|
http://www-cse.ucsd.edu/~fritz/rijndael.html
(335 words)
|
|
| |
| | UnrealScript Language Reference |
| | Object references may also contain a special value called "None", which is the equivalent of the C "NULL" pointer: it says "this variable doesn’t refer to any object". | | | If the object is in a state, and an implementation of the function exists somewhere in that state (either in the actor’s class or in some parent class), the most-derived state version of the function is called. | | | Object is the parent class of all objects in Unreal. |
|
http://unreal.epicgames.com/UnrealScript.htm
(335 words)
|
|
| |
| | Deploying Your Application |
| | This reference implementation is made available to help gauge the effort and complexity of more-detailed object-relational persistence. | | | Application logic must ensure dangling references do not occur when the contained object is removed. | | | This makes it possible to avoid dangling references when the object is deleted. |
|
http://e-docs.bea.com/wlcs/docs20/comp/deploy.htm
(2004 words)
|
|
| |
| | i501040p.txt |
| | Implements policy, assigns responsibilities, and prescribes procedures under reference (a) for implementation and use of MC programs. | | | POLICY It is DoD policy under reference (a) that a MC Program be established to review, evaluate and report on the effectiveness of MCs in the Department of Defense, and to take appropriate action to identify and correct ineffective MCs and to establish MCs when warranted. | | | Under OMB Circular A-123 (reference (c)), ...management controls should be an integral part of the entire cycle of planning, budgeting, management, accounting, and auditing. |
|
http://www.dtic.mil/whs/directives/corres/text/i501040p.txt
(4642 words)
|
|
| |
| | reference counting in Py3K Python Dev |
| | Reference counting is an implementation detail, and isn't a part of the | | | > Reference counting is an implementation detail, and isn't a part of | | | worry about memory allocation, exception labels, or reference counting, so |
|
http://www.gossamer-threads.com/lists/python/dev/425428
(3425 words)
|
|
| |
| | nsIWeakReference |
| | By now you've probably noticed that this particular weak reference implementation doesn't give you exactly the interface you were hoping for. | | | If, for instance, this owning reference is part of a cycle of owning references (e.g., if the referenced object also holds a owning reference back to you), then none of the objects in the cycle can be reclaimed without taking special measures. | | | The weak reference doesn't artificially extend the life of the observer, and yet, it can never dangle. |
|
http://www.mozilla.org/projects/xpcom/weak_references.html
(3425 words)
|
|
| |
| | Reference Counting |
| | When a Tcl variable is set to the handle for a Java object, the reference count of the TclObject that holds the Java object is incremented. | | | In Jacl, a handle is considered active as long as one TclObject holds a reference. | | | While the Tcl Blend implementation of ref counting is significantly more complex that Jacl, the end user should not see any differences between the two implementations at the script or Java code level. |
|
http://tcljava.sourceforge.net/docs/TclJava/JavaRefCount.html
(1023 words)
|
|
| |
| | LWN: Patch: Remove module reference counting. |
| | This broke partition scanning, and was immediately reverted, leaving us with a module reference count scheme identical to the previous one (just a faster implementation): we still have cases where modules can be access on failed load. | | | Then Dave decided that the work of reference counting network driver modules everywhere is too invasive, so network driver modules now have zero reference counts always. | | | D: The payoff (other than lack of complexity) is that reference D: counting disappears. |
|
http://lwn.net/Articles/41337
(1428 words)
|
|
| |
| | PowerPC Microprocessor Common Hardware Reference Platform Book 1 changes |
| | Hardware and Software Implementation Note: Platform vendors should embed vendor-specific information in their flash images to identify the firmware unambiguously and to ensure that the firmware will operate correctly on the platform. | | | Platform Implementation Note: The existence of this sensor state reporting capability should not be construed as a requirement to have any limits on sensors or to always have all four limits. | | | The platform may want to output indicators that we do not know of, the platform may have different triggers for resume than for normal power on, etc. So we are thinking of using hibernate with a null block list (first word, length in bytes, of the block list is 0). |
|
http://www-1.ibm.com/servers/eserver/pseries/library/chng_c10.html
(1428 words)
|
|
| |
| | JaxMeAPI: A clean room implementation of the JAXB API |
| | The reference implementation is now distributed from Java Dot Net. | | | In terms of Jar files, the JaxMeAPI is equivalent to the following Jar files from the reference implementation: | | | JaxMeAPI is clean room implementation of the JAXB API. |
|
http://ws.apache.org/jaxme/api/
(1428 words)
|
|
| |
| | GotW #45: Reference Counting - Part III |
| | The key to what we're about to do is quite simple: It turns out that if we do things right we only need to lock access to the reference count itself. | | | Here is a thread-safe implementation of String that assumes we have three functions: an IntAtomicGet, and IntAtomicDecrement and IntAtomicIncrement that safely return the new value. | | | For the String copy constructor, note that we can assume that the other String's data buffer won't be modified or moved during this operation, since it's the responsibility of the caller to serialize access to visible objects. |
|
http://www.gotw.ca/gotw/045.htm
(2871 words)
|
|
| |
| | Java Doesnt Pass By Value |
| | Since objects in java are never held by value it is convenient to ignore the implementation details and just say that objects are passed by reference in java. | | | That you cannot pass references to a few things (parameter memory, local variable memory, and instance variable memory) is mildly interesting and somewhat precludes the amusing notion of "out" parameters. | | | Java appears to pass objects by reference instead of by value. |
|
http://c2.com/cgi/wiki?JavaDoesntPassByValue
(2871 words)
|
|
| |
| | Open Systems Interconnection Reference Model |
| | That is the reason why OSI is often referred to as a "reference model" - other network architectures are often compared with the services specified in the OSI model. | | | Simplified Implementation and maintenance: Since the networking system is complex, breaking it into layers and specifying specific functions for a specific layer eases the implementation of the networking architecture. | | | Andrew S. Tanenbaum defines computer network to mean "an interconnection collection of autonomous computers". |
|
http://home.hetnet.nl/~ewslagmolen/osi.htm
(3029 words)
|
|
| |
| | PowerPC Linux Box |
| | Apple, IBM and Motorola originally defined two different hardware platforms for desktop computers based on the PowerPC: the PowerPC Reference Platform (PReP) and the Common Hardware Reference Platform (CHRP). | | | The purpose of the RTAS is to abstract the actual implementation of some of the hardware devices, such as: access to the PCI controller to make memory mapping and configuration cycles, access to the NVRAM, access to the RTAS, access to power management services, aiding the OS in low-level fault diagnostics. | | | By using this principle, the OS no longer needs to know the individual chip sets in a system, as is the case in the PC world, and similarly the chip set implementation is not constrained by the need to be backwards register compatible with older versions. |
|
http://choyer.homepage.dk
(3029 words)
|
|
| |
| | ALA Abstracts |
| | We wanted to know how digital reference services were started in their libraries and if these librarians have shared similar or common experiences in inception, development, and implementation. | | | Reference librarians have converted a significant portion of library resources to electronic format and are now beginning to move the reference interview itself to the electronic environment. | | | This exploratory study was designed to produce a preliminary sense of reference librarians&; experiences in adapting reference practice to the digital environment, to relay their descriptions of their own views about what is special or unique about digital reference, and to contemplate the implications of those views. |
|
http://www.ala.org/ala/rusa/rusapubs/rusq/contents/abstracts/abstracts.htm
(3029 words)
|
|
| |
| | Frequently Asked Questions (FAQs) on the LabVIEW 5.0 VI Server - KnowledgeBase - Support - National Instruments |
| | The Call By Reference function uses these same semantics and, except for determining which VI actually gets called until the last possible moment (i.e., dynamically linked), is almost identical in implementation to a normal (statically linked) subVI call. | | | Therefore, you should organize your code to open the VI reference once in an initialization stage, then use that reference whenever you want to call the VI using the Call By Reference function, then close the reference in a cleanup stage. | | | Yes, it is faster to open a VI reference once (incurring the expense of load time only once) and use that reference for multiple calls to the referenced VI. |
|
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/b053683b4aa9f52c862565f0005470e9?OpenDocument
(1127 words)
|
|
| |
| | NuView Simplifying Enterprise Data Management |
| | A Global Namespace enables the implementation of a tiered storage architecture by transparently facilitating the movement of reference data off of expensive primary storage onto less expensive secondary storage, based on administrator-defined criteria. | | | Reference data is information that is fixed, but needs to be kept available either for regulatory, informational or business purposes. | | | End user access to data is not impacted by migrating data to other tiers of storage, as data migration is transparent and the Global Namespace is automatically updated when data is moved |
|
http://www.nuview.com/Solutions/DLM.asp
(1127 words)
|
|
| |
| | IT-Director.com: More on Reference Data Management |
| | In practice, the idea behind reference data management is to manage a "single version of the truth" that is valid across the enterprise. | | | In principal Syn~ReferenceData can be used in any environment, but Coexis has a long history within trading environments and it has pre-built various best-practice modules, particularly for managing counterparties, so that a large part of the reference data management environment is already available, in template form, for this sector. | | | Typical installations cost well into seven figures, but this is not because of the hardware or software costs, but more because of the discovery procedures that need to precede any implementation. |
|
http://www.it-director.com/article.php?articleid=10850
(1127 words)
|
|
| |
| | IT-Director.com: Reference Data Management |
| | From an architectural point of view, the implementation of an RDM needs to be in some sort of hub arrangement, whereby the reference data can be accessed by any application that requires it. | | | It is therefore not surprising that there is no formal definition of what reference data is. One vendor that is working on this issue (unfortunately I am not at liberty to tell you who this is) defines it as any corporate data that needs to be shared. | | | So it might be more useful to qualify this definition by saying that reference data is any data that needs to be shared across systems. |
|
http://www.it-director.com/article.php?id=3592
(1127 words)
|
|
| |
| | SourceForge.net: Project Info - Python Weak Reference Ext. |
| | This project presents an implementation of a "Weak Reference" C extension object for CPython. | | | A Weak Reference C++ extension for Python 2.0 | | | NewsForge--online technology news on Open Source, Linux and IT |
|
http://sourceforge.net/projects/pyweakreference
(1127 words)
|
|
| |
| | Capco - Reference Data Services |
| | As a trusted advisor and partner, we help you accomplish your reference data goals and objectives, from strategy to implementation and migration. | | | While most firms have begun to acknowledge the strategic importance of an end-to-end comprehensive reference data management solution, many continue to struggle with centralizing, consolidating and migrating reference data across the enterprise. | | | In the financial services industry, reference data is at the core of the entire trade process. |
|
http://www.capco.com/crds.aspx?id=39
(1127 words)
|
|
|
