IDL Written
Standardize Wildcards
Servers accept wildcards in IDL 1.0 but there was no standard wildcard syntax. This has been addressed with a comment in the IDL on RequestFilter that says * matches any number of characters and ? matches any single character like a glob.
460@roundup
Merge Sites into Channels
The only unique information in a site was its code and location which didn't really justify another level in the network object hierarchy. The location and site code are now contained directly by the Channel object.
229@roundup
NetworkExplorer Takes RequestFilters in locate_channels and request_channels
The new request_channels method and modified locate_channels method allow a query like EventFinder.query_events which allows more filtering of the channels to happen on the server side.
445@roundup
Plottable extends SeismogramAttr
Rather than have Plottable objects as a completely seperate type of time series, they now extend SeismogramAttr giving them more in common with other TimeSeries in Fissures.
226@roundup
IfEvent Overhaul
EventAccess, EventAttr and Origin have all been folded into a single valuetype Origin. EventFinder.query_events now returns these Origins directly rather than the EventAccess object.
436@roundup
Removal of Unused IDL
Most of the write methods in IDL have never been used, so rather than continue to clutter the read only interfaces with them they're being removed completely for now. This does not preclude their being resurrected as a seperate set of write interfaces referencing the core IDL.
Also, several completely unused idl files are being dropped from the core IDL completely.
- IfService.idl
- IfTravelTimeCalculator.idl
- IfSeismogramMgr.idl
- IfRealTimeCollector.idl
- IfParameterMgr.idl
- IfPickMgr.idl
- IfFilter.idl
- IfDataSetMgr.idl
434@roundup
457@roundup
438@roundup
435@roundup
Struct to Valuetype
All structs have been changed to valuetypes. This allows for get and set methods to be used instead of direct field access. This aligns more closely with Java practices and allows for proxy objects and code to be placed in front of the object access for various reasons. This required a major reworking of most Fissures types and pretty much touches all existing code.
A fairly lengthy discussion in 441@roundup
Exception Overhaul
Rather than have every DHI method that can have problems either internally or with the request the client has sent throw FissuresException, specific exception types will be used. Other problems that might happen but are rare or can be avoided by well coded clients use corba system exceptions, in particular UNKNOWN. This followed from a long discussion which concluded with the notion that a checked/declared exception only makes sense if the client code can actually do something in response. If the client's only recourse is to put up a dialog to the user, then there is no need to have a checked exception as no new information is being added above "something went wrong". In places where the server gets into internal trouble, CORBA runtime exceptions will be used. See Exception Guidelines for a more thorough discussion of exceptions in Fissures.
439@roundup
Moment Tensor Definition
A definition for moment tensors has been added to the event servers. The definition is in the Harvard representation, but other moment tensor providers like Berkely have confirmed that it contains all the necessary fields from their representations as well.
442@roundup
Queue Seismograms Supports Partial Retrieval
The queue seismogram set of calls in SeismogramDC have been reworked such that rather than queing the request, and returning later to retrieve it in one large chunk, pieces of the request can be retrieved as the server prepares them.
437@roundup
