http://www.omg.org/technology/documents/idl2x_spec_catalog.htm
Corba language mapping specs., including Corba.
http://omniorb.sourceforge.net/docs.html
omniORB 4.1.x omniORB user’s guide . omni thread abstraction omniNames omniORB utilities omniidl for back-end authors
http://www.gnome.org/projects/ORBit2/python/dynamic_idl.html Dynamic IDL Compiling
Python is a dynamic language, so why not take advantage of it? O-P doesn’t use stubs or skeletons like most other ORBs, but instead compiles IDL files at run-time. This means incremental design and rapid prototyping can be done easily and quickly.
The function CORBA._load_idl() is used to load a specific IDL file. Other ORBs don’t implement this function, of course, so in order for code to be portable from these ORBs, an alternative approach must be used. This approach is called “IDL preprocessing.” When the CORBA module is imported for the first time, it scans a list of directories, naively (and quickly) parsing each IDL file to discover what modules and interfaces the IDL files provide. This list of directories is specified in the IDLPATH environment variable. If IDLPATH is unset, O-P defaults to the current directory, and the system IDL directories if they exist (/usr/share/idl and /usr/local/share/idl).
O-P hooks the import function to determine if the requested module exists in an IDL file. If it does, the IDL file is automatically parsed (using libIDL), processed into corresponding Python objects, and imported into the caller’s namespace. Note that because ORBit-Python’s CORBA module overloads the import function, you must import CORBA before importing any IDL modules.
When an IDL module is being imported, O-P attempts to make intelligent decisions about which files to actually parse using libIDL. For example, if you import Bonobo, O-P really only needs to process Bonobo.idl, and not the dozen or so other Bonobo_* files. In most cases, O-P’s algorithms to narrow the list of IDL files for a module are sufficient, but sometimes they’ll fail. If this happens to you, please report it as a bug. As a work-around, you can use CORBA._load_idl() to load the correct file(s), and then import the module.
http://www.omg.org/gettingstarted/corbafaq.htm CORBA® BASICS, If you want to understand CORBA, this is the place to start! You can either read straight down the page, or click on a question to go straight to a topic that interests you.
http://www.grisby.org/presentations/py10code.html This page provides the source code described in `Distributed Applications with CORBA’, a tutorial presented at the Tenth International Python Conference.
Broadcast Engineer’s Reference Book The current and definitive reference broadcast engineers needCompiled by leading international experts, this authoritative reference work covers every aspect of broadcast technology from camera to transmitter - encompassing subjects from analogue techniques to the latest digital compression and interactive technologies in a single source.Written with a minimum of maths, the book provides detailed coverage and quick access to key technologies, standards and practices. This global work will become your number one resource whether you are from an audio, video, communications or computing background. Composed for the industry professional, practicing engineer, technician or sales person looking for a guide that covers the broad landscape of television technology in one handy source, the Broadcast Engineer’s Reference Book offers comprehensive and accurate technical information.Get this wealth of information at your fingertipsĚUtilize extensive illustrationsmore than 1200 tables, charts and photographs.ĚFind easy access to essential technical and standards data.ĚDiscover information on every aspect of television technology.ĚLearn the concepts and terms every broadcaster needs to know.Learn from the experts on the following technologies:Quantities and Units; Error Correction; Network Technologies; Telco Technologies; Displays; Colourimetry; Audio Systems; Television Standards; Colour encoding; Time code; VBI data carriage; Broadcast Interconnect formats; File storage formats; HDTV; MPEG 2; DVB; Data Broadcast; ATSC Interactive TV; encryption systems; Optical systems; Studio Cameras and camcorders; VTRs and Tape Storage; Standards Convertors; TV Studios and Studio Equipment; Studio Lighting and Control; post production systems; Telecines; HDTV production systems; Media Asset Management systems; Electronic News Production Systems; OB vehicles and Mobile Control Rooms;ENG and EFP; Power and Battery Systems; R.F. propagation; Service Area Planning; Masts Towers and Antennas; Test and measurement; Systems management; and many moreRelated Focal Press titles:Watkinson: Convergence In Broadcast and Communications Media (2001, ú59.99 (GBP)/ $75.95 (USD), ISBN: 0240515099)Watkinson: MPEG Handbook (2001, ú35 (GBP)/$54.99 (USD) ISBN: 0240516567)
http://www.cs.wustl.edu/~schmidt/TAO.html TAO Overview Obtaining TAO Building TAO Documents The TAO FAQ CORBA Overview ACE and CIAO Overview JacORB & ZEN Overview TAO team members TAO Developers Forums TAO Sponsors Commercial Support Who is Using TAO TAO 3rd Party Integrators
http://www.cs.wustl.edu/~schmidt/corba-overview.html Overview of CORBA
The Common Object Request Broker Architecture (CORBA) [OMG:95a] is an emerging open distributed object computing infrastructure being standardized by the Object Management Group (OMG). CORBA automates many common network programming tasks such as object registration, location, and activation; request demultiplexing; framing and error-handling; parameter marshalling and demarshalling; and operation dispatching. See the OMG Web site for more overview material on CORBA. See my CORBA page for additional information on CORBA, including our tutorials and research on high-performance and real-time ORBs. Results from our research on high-performance and real-time CORBA are freely available for downloading in the open-source TAO ORB.
http://publib.boulder.ibm.com/infocenter/adiehelp/ Note: In future releases, IBM intends to remove the C++ Object Request Broker (ORB), the C++ library for IDL valuetypes and the WebSphere Application Server C++ security client. IBM will no longer ship or support the Common Object Request Broker Architecture (CORBA) C++ Developer Kit. The CORBA technology is a bridge for migration to a Java 2 Platform Enterprise Edition (J2EE) and WebSphere Application Server environment. It is recommended that customers migrate to the Object Request Broker (ORB) service for Java technology that ships with WebSphere Application Server. However, there is no equivalent J2EE functionality for the C++ security client or the C++ Valuetype library. Customers that require such functionality must provide or develop their own. For information on the ORB service for Java technology, see Managing Object Request Brokers.
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cpc/prggde20/corbtut.htm Writing a CPC CORBA Client, Comparison to Script Language, Typical Client Program Flow, CORBA Name Server Usage, SessionFactory and Session IDL, Starting a Session, Session Naming Context Contents, Service Object , Commands, ServiceObjectManager::create, Creating a Service, ServiceObjectManager::getDetails, Get Service Details, Fabric and Service Elements, NetworkElementFactory IDL, Network Element Methods, Creating a Logical Port, Lister IDL, Lister Example - Find a Physical Port, Transaction Manager IDL, Using Transaction Manager, NNI Resiliency Manager IDL, Using NNI Resiliency Manager, UNI Resiliency Manager IDL, Using UNI Resiliency Manager, Event Management IDL, Configuring Events, Receiving Events, Ending a Session, Complete Examples,
