The reference count should really be maintained within the event handler. This approach was taken to allow for backward compatibility and quick implementation. One approach for maintaining backward compatibility while implementing reference counting within the event handler is to create an ACE_Ref_Counted_Event_Handler "mix-in" class that concrete ACE_Event_Handlers can inherit from (i.e. multiple inheritance). Thus, legacy non-reference counted event handlers need not pay for reference counting resources.
-Strings with embedded newlines cause the import to fail -Strings with embedded quotes " cause the import to fail -Importing/exporting for values in the root section does not work -Add dynamic buffer when importing. currently it will not allow importing of values greater than a fixed ammount (4096 bytes)
The idea behind this class was to use linear regression to determine if the throughput was linear or exhibited jitter. Unfortunately it never worked quite right, so only average throughput is computed.
the unused mask argument is probably quite useful, but we ignore it, why? In fact the following comment probably relates to that: This could be made shorter if we know which *kind* of event we were about to get. Here we use <select> to find out which one might be available.
One class per-Service_Object seems wasteful. It should be possible to define a single class and re-use it for all the service objects, just by passing the Service_Descriptor as an argument to the constructor.
We maybe should move a lot of the code in ACE_OS::cuserid here so it is treated the same as the above ace_difftime and ace_timezone. But since there is a good deal more code in ACE_OS::cuserid, we probably need to move some of it off into some sort of emulation function.
Generated on Thu Feb 10 20:36:56 2005 for ACE by