diff options
Diffstat (limited to 'TAO/docs/releasenotes/index.html')
| -rw-r--r-- | TAO/docs/releasenotes/index.html | 606 |
1 files changed, 240 insertions, 366 deletions
diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html index 2e1c82cbda4..03d5a386740 100644 --- a/TAO/docs/releasenotes/index.html +++ b/TAO/docs/releasenotes/index.html @@ -1,7 +1,7 @@ <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <head> - + <title>TAO Release Information and TODO List</title> </head> <body text="#000000" bgcolor="#FFFFFF"> @@ -25,10 +25,7 @@ release</a> of <a href="http://www.cs.wustl.edu/~schmidt/TAO.html">TAO</a>: <a href="#pp">Pluggable Protocols</a></li> <li> -<a href="#poa">Portable Object Adapter (POA)</a></li> - -<li> -<a HREF="../poa_migration.html">POA Migration Notes</a></li> +<a href="#poa">Portable Object Adapter</a></li> <li> <a href="../implrepo/status.html">Implementation Repository</a></li> @@ -37,10 +34,7 @@ release</a> of <a href="http://www.cs.wustl.edu/~schmidt/TAO.html">TAO</a>: <a href="#interfrepo">Interface Repository</a></li> <li> -<a href="OBV.html">Object-by-Value</a></li> - -<li> -<a href="#nservices">CORBA Naming Service </a>and <a href="../INS.html">Interoperable Naming Service</a></li> +<a href="#nservices">CORBA Naming Service</a></li> <li> <a href="#tservices">CORBA Trading Service</a></li> @@ -52,7 +46,7 @@ release</a> of <a href="http://www.cs.wustl.edu/~schmidt/TAO.html">TAO</a>: <a href="#cservices">CORBA Concurrency Service</a></li> <li> -<a href="#av">CORBA Audio/Video Streaming Service</a></li> +<a href="#av">CORBA Audio/Video Control Service</a></li> <li> <a href="#ts">CORBA Time Service</a></li> @@ -70,7 +64,7 @@ release</a> of <a href="http://www.cs.wustl.edu/~schmidt/TAO.html">TAO</a>: <a href="#logging">TAO's Logging Service</a></li> <li> -<a href="#apps">Test & Tests</a></li> +<a href="#apps">Test & Performance Tests</a></li> <li> <a href="#ace">ORB-related ACE Changes</a></li> @@ -97,18 +91,13 @@ A complete list of all modifications to TAO is available in the <a href="http:// <a NAME="idl"></a>IDL Compiler</h3> Point of contact: <a href="mailto:gokhale@research.bell-labs.com">Aniruddha Gokhale</a> -<p>Current status: (As of May 15, 1999.) +<p>Current status: (As of Jan 22, 1999.) <ul> <li> Generated code closely follows the C++ Mapping specified in the latest C++ mapping for CORBA 2.3 (Document ptc/98-09-03).</li> <li> -We are now able to handle recursive types. We are also able to -generate optimized typecodes. -</li> - -<li> Struct members of type strings and arrays of strings now use the managed type instead of the _var type. This change was necessary to conform to the IDL->C++ mapping.</li> @@ -174,14 +163,13 @@ Verified support for the "long long" and "unsigned long long" datatypes. On platforms that do not support 64 bit longs we provided <i>partial</i> emulation through ACE_U_LongLong.</li> -<li> Perfect Hashed Operation Lookup Strategy has been added to the -IDL Compiler. -P flag to <code>tao_idl</code> enables the perfect -hased lookup strategy. This strategy uses <a -href="http://www.cs.wustl.edu/~schmidt/gperf.ps.gz">GPERF</a>, the -GNU's Perfect Hash Function Generator written by Dr.Douglas -C. Schmidt. Right now, GPERF works only on Solaris. Any work on -porting GPERF to other platforms will be highly -appreciated.</L1></li> +<li> +Perfect Hashed Operation Lookup Strategy has been added to the IDL Compiler. +-P flag to the <tao_idl>enables the perfect hased lookup strategy. +This strategy uses <a href="http://www.cs.wustl.edu/~schmidt/gperf.ps.gz">GPERF</a>, +the GNU's Perfect Hash Function Generator written by Dr.Douglas C. Schmidt. +Right now, GPERF works only on Solaris. Any work on porting GPERF to other +platforms will be highly appreciated. </L1></li> <li> Significantly improved the support for unions. The default case is yet @@ -197,15 +185,15 @@ templates have problems on most compilers.</li> <li> The <<= and >>= operators for user-defined types are now generated.</li> -<li> Completely redesigned the IDL compiler using the Visitor -patterns. Many incomplete issues have been resolved. These include -support for "sequence of typecodes", passing object references as in, -inout, and out parameters. Code generation for sequences is also -properly handled i.e., for a named sequence such as <CODE>typedef -sequence<char>CharSeq;</CODE>, we now generate a new class (and -hence a type) called "class CharSeq". Arrays are still being worked -out and will be done soon. An important difference in the generated -code is that the skeletons now use a table driven approach very +<li> +Completely redesigned the IDL compiler using the Visitor patterns. Many +incomplete issues have been resolved. These include support for "sequence +of typecodes", passing object references as in, inout, and out parameters. +Code generation for sequences is also properly handled i.e., for a named +sequence such as "typedef sequence <char>CharSeq;", we now generate +a new class (and hence a type) called "class CharSeq". Arrays are still +being worked out and will be done soon. An important difference in the +generated code is that the skeletons now use a table driven approach very similar to the stubs.</li> <li> @@ -254,8 +242,8 @@ is mainly contained in the generated header file directly in the class declaration.</li> <li> -The IDL Compiler generates templates for servant implementations. The options -are -GI [ h | s | b | e | c ]</li> +The IDL Compiler generates templates for servant implementations. The options +are -GI [ h | s | b | e | c ]</li> </ul> <p><br>Known bugs/unimplemented constructs: @@ -291,6 +279,18 @@ include support for Unions.</li> Use <a href="http://www.cs.utah.edu/projects/flux/flick/">Flick</a> (from the University of Utah) to generate compiled stubs.</li> +<br> +<p> +<br> +<br> +<br> +<br> +<br> +<br> +<br> +<br> +<br> +<br> <p>Goal is to measure the code size of the interpretive stubs generated by TAO IDL compiler <i>vs</i> code size of compiled stubs. Then compare the performance of each. We want to prove the thesis that TAO IDL compiler @@ -303,15 +303,13 @@ of size/performance/determinism will be made. Tweak the IDL compiler to generate code that's more easily integrated back into the ORB Core, e.g., POA, etc. This will depend largely on our ability to generalize the changes necessary to generated code.</li> +</ul> <li> The generated sequence classes should not be generated per sequence, but per type and parent scope. Which means, that the overhead of having the source code generated serveral times should be reduced. To do this, an -extra pass over the internal representation of the IDL file has to be done.<P> -</ul> - - +extra pass over the internal representation of the IDL file has to be done. <hr></li> <br><!--#include virtual="orbcore.html" --> @@ -380,7 +378,6 @@ shared memory and system buses like PCI or VME.</li> Current Status: <ul> <li> - The initial prototype of the basic framework to support pluggable transport protocols has been compiled, linked and, tested against an older version of TAO. The standard TAO regression tests @@ -434,263 +431,202 @@ and transport protocols for a given platform.</li> <hr> <h3> -<a NAME="poa"></a>Portable Object Adapter (POA)</h3> +<a NAME="poa"></a>Portable Object Adapter</h3> Point of contact: <a href="mailto:irfan@cs.wustl.edu">Irfan Pyarali</a> - -The POA associates servants with the ORB and demultiplexes incoming -requests to servants. <P> - <p>Current Status: <ul> <li> -TAO supports the POA spec. This section will carry updates as available.</li> +TAO fully supports the POA spec. This section will carry updates as available.</li> </ul> Known issues: - <ul> - -<li> ORB::shutdown needs to deactive the POA Managers. We need to fix -this. </li><P> - -</UL> - +<li> +The synchronization in the POA is broken. For example, the locks are held +across the invocation on the servant. The locks are also held across the +invocation on the AdapterActivator. This forces the use of recursive locks +inside the POA. However, the problem with recursive locks is that multiple +threads cannot dispatch requests on the same POA simultaneous.</li> + +<br> +<p> +<br> +<br> +<br> +<br> +<li> +Add the new RefCountServantBase class to TAO. This reference counted base +class was added to the CORBA specification to avoid race conditions for +servant deletion in threaded servers. <a href="ftp://ftp.omg.org/pub/docs/orbos/98-07-12.pdf">ftp://ftp.omg.org/pub/docs/orbos/98-07-12.pdf</a> +contains the relevant text.</li> + +<br> +<p> +<br> +<br> +<br> +<br> +<li> +Currently, the complete POA name is used as the POA identity. This scheme +is inefficient in many ways including: (a) the complete POA name can be +significantly large in size, and therefore, ineffient to pass with every +method call from the client to the server; (b) it is varible in size, and +therefore, does not lend itself to smart and effective parsing; (c) the +searching based on the complete POA name is very ineffient.</li> + +<br> +<p> +<br> +<br> +<p>The correct solution here is to use an active demux table, and flatten +the POA hierarchy. This will help in the searching since active demuxing +is fast and predictable. This will also help in the parsing since the demux +key will be fixed size. +<p>Note that for persistent ids, we have to pass the complete POA name +in addition to the demux key in order to handle POA creation on demand. +<li> +Timestamps in persistent IORs are note required. They should be removed.</li> + +<li> +POA exceptions should be removed from the list of system exceptions.</li> + +<li> +We need to separate out the POA functionality required to support the full +CORBA spec from the POA functionality required to support the Minimal CORBA +spec.</li> + +<li> +We need to investigate whether it feasible for us to provide active demuxing +for the USER_ID policy. Currently, the best we do with the USER_ID policy +is a hash table based demuxing.</li> + +<br> +<p> +<br> +<br> +<p>Note that we have to pass the user id in addition to the demux key in +order to handle servant creation on demand. +<li> +We can potentially add active demuxing for method name lookup. The benefit +of this optimization is questionable since the current perfect hashing +scheme provide very good and predictable behavior.</li> + +<br> +<p> +<br> +<br> +<p>Also, note that this optimization will require many changes. We would +have to use the help of the IDL compiler to modify the object key that +is passed for every method call differently. Note that this scheme doesn't +work in the case of multiple inheritance or when the client stubs are not +TAO. +<li> +There are some POA objects in a typical server that are not freed up properly, +resulting in a memory leak. This is not very significant since the leak +does not grow. However, it still needs a fix.</li> + +<br> +<p> +<br> +<br> +<br> +<br> </ul> Future work: <ul> +<li> +Determine the degree to which we will support the full semantics of remote +objects on a collocated object. The spec mandates that collocated object +should behave <i>exactly</i> like remote objects, but that means that request +will have to be queued rather than calling a method directly, and this +could be hazardous to our quest for real-time ORB status.</li> -<li> Determine the degree to which we will support the full semantics -of remote objects on a collocated object. The spec mandates that -collocated object should behave <i>exactly</i> like remote objects, -but that means that request will have to be queued rather than calling -a method directly, and this could be hazardous to our quest for -real-time ORB status.</li><P> - -</ul> - -Recently completed work:<P> +<li> +Provide extensions of the specification to ensure real-time delivery of +messages.</li> +<br> +<p> +<br> +<br> +<br> +<br> </ul> +Recently completed work: +<br> +<br> <ul> +<li> +Support for collocation should be much better now because the POA can tell +if we created the object reference.</li> -<li> TAO's POA now properly supports both the threading policies: -SINGLE_THREAD_MODEL and ORB_CTRL_MODEL. </li><P> - -<li>The synchronization in the POA is now very optimal. For example, -the locks are not held across the invocation on the servant. The locks -are also not held across the invocation on the AdapterActivator and -ServantManagers. This allows us to use regular locks instead of -recursive locks inside the POA. This also allows multiple threads to -dispatch requests on the same POA simultaneous.</li><P> - -<li>TAO now supports reference counting between POA and servants, -including the new RefCountServantBase and ServantBase_var -classes. RefCountServantBase is a reference counted base class that -was added to the CORBA specification to avoid race conditions for -servant deletion in threaded servers. <a -href="ftp://ftp.omg.org/pub/docs/orbos/98-07-12.pdf">ftp://ftp.omg.org/pub/docs/orbos/98-07-12.pdf</a> -contains the relevant text. Check <a -href="../poa_migration.html#Reference counting Servants">here</a> on -some hints to avoid trouble.</li><P> - -<li> The POA now supports active demultiplexing of servants in the -SYSTEM_ID and the USER_ID policy. This should make the POA faster and -more predictable since there is no hashing involved and the index of -the slot where the servant is registered is in the Object Key.</li> -<P> - -<li> Previously, the complete POA name was used as the POA -identity. This scheme was inefficient in many ways including: (a) the -complete POA name can be significantly large in size, and therefore, -ineffient to pass with every method call from the client to the -server; (b) it is varible in size, and therefore, does not lend itself -to smart and effective parsing; (c) the searching based on the -complete POA name is very ineffient.</li> - -<p> The new solution is to use an active demux table, and flatten the -POA hierarchy. This will help in the searching since active demuxing -is fast and predictable. This will also help in the parsing since the -demux key will be fixed size. - -<p> Note that for persistent ids, we have to pass the complete POA -name in addition to the demux key in order to handle POA creation on -demand.<P> - -<li> There were some POA objects in a typical server that are not -freed up properly, resulting in a memory leak. This has now been -fixed.</li> <P> - -<li> Timestamps in persistent IORs were not required and have been -removed.</li> <P> - -<li> POA exceptions are not not system exceptions and have been -removed from the list of system exceptions.</li> <P> - -<li> Vastly improved the ability of the POA to deal with user -exceptions, memory allocation failures, and constructor failures.</li> -<P> - -<li> We now support a minimal POA for the minimal CORBA -specification.</li> <P> - -<li> We have decided not to support active demuxing for method name -lookup. The benefit of this optimization was questionable since the -current perfect hashing scheme provide very good and predictable -behavior.</li> <P> - -Also, note that this optimization will require many changes. We would -have to use the help of the IDL compiler to modify the object key that -is passed for every method call differently. Note that this scheme -doesn't work in the case of multiple inheritance or when the client -stubs are not TAO.<P> - -<li> Improved the parsing of object keys belonging to the -RootPOA. Since this is the default POA and is commonly used, we have -given it a reserved byte in the object key in order to quickly -identify it. With the reserved bit, the active demux key for the -RootPOA is not used, and no map lookups are required.</li> <P> - -<li> POA name separator was changed from '/' to '\0'. Since POA names -are strings, this makes a better choice since there is no chance of a -conflict with the string specified by the user. </li> <P> - -<li> We have support for reactivating servants with system generated -ids. </li> <P> - -<li> The TAO specific synchronization POA policy has been -removed. </li> <P> - -<li> New examples have been added to show how servants can be -dynamically loaded from DLLs on demand. </li> <P> +<li> +The POA now supports active demultiplexing of servants in the SYSTEM_ID +policy. This should make the POA faster and more predictable since there +is no hashing involved and the index of the slot where the servant is registered +is in the Object Key.</li> -<li> Support for collocation should be much better now because the POA -can tell if we created the object reference.</li><P> +<br> +<p> +<br> +<br> +<br> +<br> </ul> -</UL> <hr> <h3> <a NAME="interfrepo"></a>Interface Repository</h3> -Point of contact: <a href="mailto:parsons@cs.wustl.edu">Jeff Parsons</a><P> - -The Interface Repository provides run-time information about IDL -interfaces. Using this information, it is possible for a program to -encounter an object whose interface was not known when the program was -compiled, yet, be able to determine what operations are valid on the -object and make invocations on it using the DII. - -<p>Current Status: TDB -<p>Known Issues: TDB -<p>Recent Work: TDB -<p>Future Work: TDB +Point of contact: <a href="mailto:parsons@cs.wustl.edu">Jeff Parsons</a> +<p>Current Status: +<p>Known Issues: +<p>Recent Work: +<p>Future Work: <p> - <hr> - -<br><!--#include virtual="OBV.html" --> -<hr> - <h3> -<a NAME="nservices"></a>CORBA Naming Service and Interoperable Naming Service</h3> -Points of contact: <a href="mailto:marina@cs.wustl.edu">Marina -Spivak</a> and <a href="mailto:vishal@cs.wustl.edu">Vishal Kachroo</a> -<p> - -The CORBA <a href="ftp://www.omg.org/pub/docs/formal/97-07-12.pdf"> -Naming Service</a> supports a hierarchical mapping between sequences -of strings and object references. The CORBA <A -HREF="ftp://ftp.omg.org/pub/docs/orbos/98-10-11.pdf">Interoperable -Naming Service</A> defines a standard way for clients and servers to -locate the Naming Service. It allows the ORB to be administratively -configured for bootstrapping to services not set up with the orb at -install time. <P> - -<p>Current status (as of 7th Apr 1999): +<a NAME="nservices"></a>CORBA Naming Service</h3> +Point of contact: <a href="mailto:marina@cs.wustl.edu">Marina Spivak</a> +<p>Current status (as of Jan 11 1999): <ul> <li> -Implementation of the CORBA Naming Service spec is complete. TAO's -Naming Service provides an optional persistence capability.</li> -<li> -Implementation of the CORBA InterOperable Naming Service is in -progress. </li> +Implementation of the CORBA Naming Service spec is complete.</li> </ul> Recently completed work: <ul> <li> -Added support for Persistence (using memory-mapped files). Persistence -feature is optional, and is controlled by the command line argument.</li> +The implementation of the Naming Service has been upgraded to use TAO's +exception macros, which allow it to work both with C++ exceptions and without.</li> <li> -Updated the implementation of the Naming Service to use new ACE -exception macros.</li> -<li> -Added support for the InterOperable Naming Service, which enables the -ORB to support IORs in user-friendly <CODE>iioploc</CODE> format. -These features allow the ORB to be configured to return arbitrary object -references from <CODE>CORBA::ORB::resolve_initial_references</CODE> -for non-locality-constrained objects. Two options -ORBInitRef and --ORBDefaultInitRef have been added to the orb for bootstrapping to -arbitrary services. -</li> - -<li>Added support for the Naming service to act like an agent: to understand IIOP -request messages from clients and respond with reply messages with a -LOCATION_FORWARD/OBJECT_NOT_EXIST status. The Naming Service can be -configured through ORB options to register arbitrary services given -the URL-format IOR for the service. The resolve_initial_references () -resolves a service in the following order : -<br>1. -ORBInitRef -<br>2. -ORBDefaultInitRef -<br>3. Multicast to service. -</li> +Destroy method has been updated.</li> <li> -Added a test for the InterOperable Naming Service that works in -conjunction with the current TAO examples. -</li> - +More test examples have been added to TAO/orbsvcs/tests/Simple_Naming.</li> </ul> - Work in progress: <ul> - -<LI> Support for the iiopname format and conversions -to and from URL-style IORs. -</LI> - -<LI> -A detailed InterOperable Naming Service test. -</LI> - +<li> +Currently the bindings are stored as a table in memory. Work is under way +to provide persistance option for the Naming Service.</li> </ul> Future work: <ul> <li> -Support for a load balancing feature similar to the one present in ORBIX. -It will be possible to bind a group of objects under a single name, and when a client attempts to resolve the name in question, a preset policy (e.g., random, round robin, etc.) will determine which one of the object references from the group will be returned. -</li> -<li> -Update to the 'destroy' method, once the POA restructuring effort is complete, to do the "Right Thing TM". -</li> -<li> Replication of the bindings to other Naming Service's currently running. -It will probably be modeled after the LDAP Multi-Master Replication -Protocol.</li> -<li> -Support for the Naming Service to handle the IIOP -LocateRequest messages and respond with LocateReply messages with a -LOCATION_FORWARD/OBJECT_NOT_EXIST status. +It will probably be modeled after the LDAP Multi-Master Replication Protocol.</li> </ul> - +For general documentation on the Naming Service please read <a href="ftp://www.omg.org/pub/docs/formal/97-07-12.pdf">The +Naming Service Specification</a>. <p> <hr> <h3> <a NAME="tservices"></a>CORBA Trading Service</h3> Point of contact: <a href="mailto:sbw1@cs.wustl.edu">Seth Widoff</a> - -<p>The <a href="http://www.omg.org/corba/sectrans.htm#trader"> Trading -Service</a> is an implementation of the COS Trading Service -speficiation that meets the Linked Trader conformance criteria --- it -implements the <tt>Lookup</tt>, <tt>Register</tt>, <tt>Admin</tt>, and -<tt>Link</tt> interfaces, but not the <tt>Proxy</tt> -interface. Notably, the TAO trader supports the following features:<P> -<ul> <li> Multithreaded operation;</li> +<p>The TAO Trading Service is a transient implementation of the COS Trading +Service speficiation that meets the Linked Trader conformance criteria +--- it implements the <tt>Lookup</tt>, <tt>Register</tt>, <tt>Admin</tt>, +and <tt>Link</tt> interfaces, but not the <tt>Proxy</tt> interface. Notably, +the TAO trader supports the following features: +<ul> +<li> +Multithreaded operation;</li> <li> Trader federations and distributed queries;</li> @@ -719,110 +655,66 @@ The Proxy Interface.</li> <li> Persistent storage of service types and offers.</li> </ul> +For general documentation of the Trading Service, please read <a href="http://www.omg.org/corba/sectrans.htm#trader">The +Trading Service Specification.</a> <p> <hr> <h3> <a NAME="pservices"></a>CORBA Property Service</h3> -Point of contact: <a href="mailto:alex@cs.wustl.edu">Alexander Babu -Arulanthu</a> - -<p>Current status (as of Mar 9th, 1999): All the interfaces of this -service have been implemented. Please -go through the test examples at $TAO/orbsvcs/tests/CosPropertyService. -Property Service is has been used by the TAO's <a href="#av">Audio Video Streaming -Service</a>developed for TAO. For general documentation of the -Property Service, please read <a -href="http://www.omg.org/corba/sectrans.htm#prop">The Property Service -Specification.</a> - -<P>Recent Work: -<ul> - <li> - Changed the PropertyException from Exception to struct, according - to the OMG's changes. - </li> - <li> - Changed the implementation to allocate storage for the Sequence - out parameters, eventhough their length is 0. This is according - to the CORBA specification. - </li> -</ul> - +Point of contact: <a href="mailto:alex@cs.wustl.edu">Alexander Babu Arulanthu</a> +<p>Current status (as of May 02, 1998) +<p>All the interfaces of this service have been implemented. Please +go through the test examples at $TAO/orbsvcs/tests/CosPropertyService. +Property Service is now used by the AVStreams that is currently being +developed for TAO. More testing is being done. +<p>For general documentation of the Property Service, please read <a href="http://www.omg.org/corba/sectrans.htm#prop">The +Property Service Specification.</a> <p> <hr> <h3> <a NAME="cservices"></a>CORBA Concurrency Service</h3> Point of contact: <a href="mailto:tworm@cs.wustl.edu">Torben Worm</a> <p>Current status (as of May 3rd): - -The <a href="http://www.omg.org/corba/sectrans.htm#concur"> -Concurrency Service</a> provides a mechanism that allows clients to -acquire and release various types of locks in a distributed system.<P> - <ul> <li> -A simple version of the Concurrency Service has been implemented, i.e. +A simple version of the concurrency service has been implemented, i.e. a version without transactions. It is currently being tested.</li> </ul> Future Work: <ul> <li> Implementation of the Concurrency Service with transactions</li> -</ul><P> +</ul> +For general documentation of the Concurrency Service, please read +<a href="http://www.omg.org/corba/sectrans.htm#concur">The +Concurrency Service Specification.</a> <hr WIDTH="100%"> -<h3><a NAME="av"></a>CORBA Audio/Video Streaming Service</h3> -Point of contact: <a href="mailto:naga@cs.wustl.edu">Nagarajan -Surendran</a> and <a href="mailto:yamuna@cs.wustl.edu">Yamuna Krishnamurthy</a> +<h3> +<a NAME="av"></a>CORBA Audio/Video Control Service</h3> +Point of contact: <a href="mailto:naga@cs.wustl.edu">Nagarajan Surendran</a> <p>This is an implementation of the OMG spec addressing the <a href="http://www.cs.wustl.edu/~sumedh/research/corbaav.pdf">Control -and Management of Audio/Video Streams</a>.For more documentation on -TAO's A/V Service please have a look <A HREF="http://www.cs.wustl.edu/~naga/av.html">here</A>. - -<p><h4>Current Status:</h4> -<p> -<ul> - <li> - The audio/video streaming service has been implemented in the full - profile. The current implementation support all the flow related - components like flowEndpoint,FDev,FlowConnection,..,etc. - </li> - <li> - An MPEG-1 application which streams mpeg-1 video and mpeg-1 audio - separately has been developed using the service. The client side - of the mpeg player requires X windows support.Its available in - the release at $TAO_ROOT/orbsvcs/tests/AVStreams/mpeg/source. - </li> - <li> - An Integrated Video-on-demand application has been developed - using the Trading Service and the A/V Service. The demo uses a - Java FrontEnd and JNI to talk to the TAO C++ trader client. The - demo is available in the release at - $TAO_ROOT/orbsvcs/tests/AVStreams/server_discovery. - </li> -</ul> +and Management of Audio/Video Streams</a>. +<p>The audio/video streaming service has been implemented in the light +profile. An MPEG-1 application which streams mpeg-1 video and mpeg-1 audio +separately has been developed using the service. This application currently +works only for Unix platforms. <p>Work in progress: <ul> <li> -Implementing the SFP protocol. -</li> -<li> - Adding Multipoint streams support. -</li> +Implementing the SFP protocol</li> + <li> - Developing a Video-conferencing application using the A/V Service. -</li> +Integrating the mpeg-1 streaming application with the trading service.</li> </ul> <hr> <p><a NAME="ts"></a><b>CORBA Time Service</b> <p>Point of contact: <a href="mailto:vishal@cs.wustl.edu">Vishal Kachroo</a> - -<p> The <a href="ftp://ftp.omg.org/pub/docs/formal/97-02-22.pdf">Time Service</a> - allows clients to connect to Time Service Clerks and obtain globally -synchronized time. This time is calculated from the time obtained from -one or more Time Servers running on multiple machines in the -network. The service uses the TAO Implementation Repository to -activate the time servers on demand. - +<p>TAO's Time Service allows clients to connect to Time Service Clerks +and obtain globally synchronized time. This time is calculated from the +time obtained from one or more Time Servers running on multiple machines +in the network. The service uses the TAO Implementation Repository to activate +the time servers on demand. <p>Current status (as of 10th Jan 1999): <ul> <li> @@ -838,14 +730,15 @@ algorithm can be used in the future.</li> <li> Implementation of the Timer Event Service.</li> </ul> +For OMG's documentation on the Time Service please read <a href="ftp://ftp.omg.org/pub/docs/formal/97-02-22.pdf">The +Time Service Specification. (.pdf)</a> <p> - <hr WIDTH="100%"> <h3> <a NAME="ec"></a>CORBA Event Service</h3> <h4> -Last updated: Fri Mar 5 20:38:26 CST 1999</h4> +Last updated: Wed Jan 13 20:01:27 CST 1999</h4> Point of contact: <a href="mailto:pradeep@cs.wustl.edu">Pradeep Gore</a> <p>The COS compliant Event Service implements the Event Service Specification: <a href="http://www.omg.org/docs/formal/97-12-11.pdf">(.pdf)</a>, @@ -868,30 +761,23 @@ Event Service (<tt>$TAO_ROOT/orbsvcs/CosEvent_Service</tt>)The Event Service creates a COS compliant event channel and registers it with the naming service with the default name "CosEventChannel".</li> -<br>Please read the associated README for more details. +<br>Please read the associated README for more details.</ul> -<li> -CosEC_Multiple: <tt>($TAO_ROOT/orbsvcs/tests/CosEC_Multiple)</tt>: -This test demonstrates how multiple CosEC's connect to one RtEC and how -multiple consumers and producers exchange events in this configuration.</li> -</ul> <h3> -Known bugs:</h3> +Current Work:</h3> + <ul> <li> -CosEC_Multiple: <tt>($TAO_ROOT/orbsvcs/tests/CosEC_Multiple)</tt>: -Once the tests are done, the control doesn't return to the shell, -you have to say CTRL-C to get back to the prompt. -</li> +CosEC_Multiple: <tt>($TAO_ROOT/orbsvcs/tests/CosEC_Multiple)</tt>: +This test demonstrates how multiple CosEC's connect to one RtEC and how +multiple consumers and producers exchange events in this configuration.</li> </ul> - -<hr WIDTH="100%"> <!--#include virtual="ec.html" --> <p> <hr> <h3> <a NAME="scheduling"></a>TAO's Scheduling Service</h3> -Point of contact: <a href="mailto:cdgill@cs.wustl.edu">Chris Gill</a> +Point of contact: <a href="mailto:cdgill@cs.wustl.edu">Chris Gill</a> and <a href="mailto:levine@cs.wustl.edu">David Levine</a> <p>Currently Implemented Features: <ul> @@ -920,25 +806,25 @@ strategy to use for that priority level.</li> Future work: <ul> <li> -Implement heap-based dispatching queues.</li> + Implement heap-based dispatching queues.</li> <li> -Add support for additional configurability, especially in the type + Add support for additional configurability, especially in the type of dispatching strategy (list vs. heap) that will be used to dispatch operations at a given static priority level.</li> <li> -Benchmark the various alternative strategies to obtain performance + Benchmark the various alternative strategies to obtain performance profiles across different operation loads and OS platforms.</li> <li> -Add increased functionality. Requests and suggestions are welcome.</li> + Add increased functionality. Requests and suggestions are welcome.</li> </ul> <hr> <h3> <a NAME="logging"></a>TAO's Logging Service</h3> -Point of contact: <a href="mailto:mjb2@cs.wustl.edu">Matt Braun</a> +Point of contact: <a href="mailto:mjb2@cs.wustl.edu">Matt Braun</a> <p>Current status (as of August 4'th): <ul> <li> @@ -948,7 +834,7 @@ from multiple clients. It is currently in the testing stage.</li> Future work: <ul> <li> -Add increased functionality. Requests and suggestions are welcome.</li> + Add increased functionality. Requests and suggestions are welcome.</li> </ul> <hr> @@ -997,20 +883,6 @@ Evolve into a testbed for discovering sources of performance non-determinism & priority inversion.</li> </ul> -<p>Pluggable: -<p>Current status: -<p>The TAO Pluggable test utilizes ACE Timeprobes to time the latency at -various points in the ORB, especially that incurred by the Pluggable Protocols -implementation. Comparisons can be made not only between different layers of the -ORB, but also between different protocols as they become available. -<p>Future work: -<ul> -<li> -Add options to redirect the output to a file.</li> -<li> -Script or otherwise automate the piping of the output to a spreadsheet.</li> -</ul> - <hr> <h3> <a NAME="ace"></a>ORB-related ACE Changes</h3> @@ -1064,6 +936,8 @@ and <a href="mailto:cdgill@cs.wustl.edu">Chris Gill</a>. <p><a href="http://www.cs.wustl.edu/~schmidt/dove.html">DOVE</a> is documented in detail <a href="http://www.cs.wustl.edu/~schmidt/Dove.ps.gz">online</a>. This discussion focuses on the following goals: +<br> +<br> <ul> <li> Have a DOVE Browser running using Java Beans as vizualization components.</li> @@ -1113,7 +987,7 @@ Enhancing MIB functionality</li> <li> Monitoring the AV Streaming Service</li> </ul> -For more information on the DOVE demo, please refer to: $TAO_ROOT/orbsvcs/tests/Simulator/README.<P> +For more information on the DOVE demo, please refer to: $TAO_ROOT/orbsvcs/tests/Simulator/README <hr> <h3> <a NAME="forwarding"></a>Location Forwarding</h3> @@ -1140,6 +1014,6 @@ Kircher</a>. <p>For more information see <a href="../locate_request.html">Locate request</a> <p> <hr> -<p>Back to the TAO <a href="../index.html">documentation index</a>.<!--#include virtual="/~schmidt/cgi-sig.html" --> +<p>Back to the TAO <a href="../index.html">documentation index</a>. <!--#include virtual="/~schmidt/cgi-sig.html" --> </body> </html> |