#include <BESCgiInterface.h>
Inheritance diagram for BESCgiInterface:
Public Member Functions | |
BESCgiInterface (const string &type, DODSFilter &df) | |
Instantiate an instance of the BESCgiInterface interface. | |
virtual | ~BESCgiInterface () |
virtual void | dump (ostream &strm) const |
dumps information about this object | |
virtual int | execute_request (const string &from) |
Executes the given request to generate a specified response object. | |
Static Public Member Functions | |
static void | add_init_callback (p_bes_init init) |
static void | add_end_callback (p_bes_end end) |
Protected Member Functions | |
virtual void | build_data_request_plan () |
Build the data request plan using the given DODSFilter. | |
virtual int | exception_manager (BESException &e) |
Manage any exceptions thrown during the whole process. | |
virtual void | initialize () |
Initialize the BES object. | |
virtual void | validate_data_request () |
Validate the incoming request information. | |
virtual void | execute_data_request_plan () |
Execute the data request plan. | |
virtual void | invoke_aggregation () |
Aggregate the resulting response object. | |
virtual void | transmit_data () |
Transmit the resulting response object. | |
virtual void | log_status () |
Log the status of the request. | |
virtual void | report_request () |
Report the request and status of the request to BESReporterList::TheList(). | |
virtual void | end_request () |
End the BES request. | |
virtual void | clean () |
Clean up after the request. | |
Protected Attributes | |
BESDataHandlerInterface | _dhi |
BESTransmitter * | _transmitter |
OPeNDAP data handlers have been mainly accessed through a CGI interface. A person goes to a website with an OPeNDAP server and makes a certain request of that server for files available to that site.
This class provides an interface into the BES framework for the CGI interface. It greatly simplifies server coding for developers using the CGI interface.
Information from the DODSFilter class is placed in the BESDataHandlerInterface and a BESContainer is built from this information so that BES can handle the request, building the proper response using the appropriate data handler. BESCgiInterface also creates a Transmitter that interacts with the DODSFilter object for sending the response back to the user.
For example, a server to handle requests for the cedar data type would look something like this:
CedarFilter df(argc, argv); BESCgiInterface d( "cedar", df ) ; d.execute_request() ;
And that's it!
DODSFilter
Definition at line 74 of file BESCgiInterface.h.
BESCgiInterface::BESCgiInterface | ( | const string & | type, | |
DODSFilter & | df | |||
) |
Instantiate an instance of the BESCgiInterface interface.
Creates a BESFilterTransmitter to transmit the response back to the caller. Only the build_data_request_plan method is implemented in this class. All other methods are inherited from BESInterface.
type | data type handled by this OPeNDAP CGI server | |
df | DODSFilter object built from command line arguments |
Definition at line 54 of file BESCgiInterface.cc.
References BESInterface::_dhi, BESInterface::_transmitter, and _BESDataHandlerInterface::transmit_protocol.
BESCgiInterface::~BESCgiInterface | ( | ) | [virtual] |
Definition at line 63 of file BESCgiInterface.cc.
References BESInterface::_transmitter, and BESInterface::clean().
Here is the call graph for this function:
void BESCgiInterface::build_data_request_plan | ( | ) | [protected, virtual] |
Build the data request plan using the given DODSFilter.
The BESDSDataHandlerInterace is built using information from the DODSFilter object passed to the constructor of this object. The constraint, data type, dataset, and action are retrieved from the DODSFilter to build the request plan.
DODSFilter
Reimplemented from BESInterface.
Definition at line 82 of file BESCgiInterface.cc.
References BESInterface::_dhi, _BESDataHandlerInterface::action, BESDEBUG, _BESDataHandlerInterface::containers, BESResponseHandlerList::find_handler(), _BESDataHandlerInterface::response_handler, and BESResponseHandlerList::TheList().
Here is the call graph for this function:
void BESCgiInterface::dump | ( | ostream & | strm | ) | const [virtual] |
dumps information about this object
Displays the pointer value of this instance along with information about the DODSFilter and the type of data handled by this interface.
strm | C++ i/o stream to dump the information to |
Reimplemented from BESInterface.
Definition at line 117 of file BESCgiInterface.cc.
References BESIndent::Indent(), BESIndent::LMarg(), and BESIndent::UnIndent().
Here is the call graph for this function:
int BESInterface::exception_manager | ( | BESException & | e | ) | [protected, virtual, inherited] |
Manage any exceptions thrown during the whole process.
Specific responses are generated given a specific Exception caught. If additional exceptions are thrown within derived systems then implement those in the derived exception_manager methods. This is a catch-all manager and should be called once derived methods have caught their exceptions.
e | BESException to be managed |
Reimplemented in BESApacheInterface.
Definition at line 393 of file BESInterface.cc.
References BESInterface::_dhi, BESExceptionManager::handle_exception(), and BESExceptionManager::TheEHM().
Referenced by BESApacheInterface::exception_manager().
Here is the call graph for this function:
void BESInterface::initialize | ( | ) | [protected, virtual, inherited] |
Initialize the BES object.
This method must be called by all derived classes as it will initialize the environment
Reimplemented in BESApacheInterface, and BESCmdInterface.
Definition at line 191 of file BESInterface.cc.
References BESInterface::_dhi, BESDEBUG, _BESDataHandlerInterface::data, and DATA_REQUEST.
Referenced by BESInterface::execute_request(), and BESCmdInterface::initialize().
void BESInterface::validate_data_request | ( | ) | [protected, virtual, inherited] |
Validate the incoming request information.
Reimplemented in BESApacheInterface, and BESCmdInterface.
Definition at line 214 of file BESInterface.cc.
Referenced by BESInterface::execute_request(), and BESCmdInterface::validate_data_request().
void BESInterface::execute_data_request_plan | ( | ) | [protected, virtual, inherited] |
Execute the data request plan.
Given the information in the BESDataHandlerInterface, execute the request. To do this we simply find the response handler given the action in the BESDataHandlerInterface and tell it to execute.
If no BESResponseHandler can be found given the action then an exception is thrown.
Reimplemented in BESCmdInterface.
Definition at line 245 of file BESInterface.cc.
References BESInterface::_dhi, _BESDataHandlerInterface::action, BESDEBUG, _BESDataHandlerInterface::data, DATA_REQUEST, BESResponseHandler::execute(), and _BESDataHandlerInterface::response_handler.
Referenced by BESCmdInterface::execute_data_request_plan(), and BESInterface::execute_request().
Here is the call graph for this function:
void BESInterface::invoke_aggregation | ( | ) | [protected, virtual, inherited] |
Aggregate the resulting response object.
Reimplemented in BESCmdInterface.
Definition at line 263 of file BESInterface.cc.
References BESInterface::_dhi, AGG_CMD, AGG_HANDLER, BESAggregationServer::aggregate(), BESDEBUG, _BESDataHandlerInterface::data, BESAggFactory::find_handler(), and BESAggFactory::TheFactory().
Referenced by BESInterface::execute_request(), and BESCmdInterface::invoke_aggregation().
Here is the call graph for this function:
void BESInterface::transmit_data | ( | ) | [protected, virtual, inherited] |
Transmit the resulting response object.
The derived classes are responsible for specifying a transmitter object for use in transmitting the response object. Again, the BESResponseHandler knows how to transmit itself.
If no response handler or no response object or no transmitter is specified then do nothing here.
Reimplemented in BESCmdInterface.
Definition at line 296 of file BESInterface.cc.
References BESInterface::_dhi, BESInterface::_transmitter, BESDEBUG, _BESDataHandlerInterface::data, DATA_REQUEST, _BESDataHandlerInterface::error_info, BESInfo::print(), _BESDataHandlerInterface::response_handler, BESResponseHandler::transmit(), and BESInfo::transmit().
Referenced by BESCmdInterface::transmit_data().
Here is the call graph for this function:
void BESInterface::log_status | ( | ) | [protected, virtual, inherited] |
Log the status of the request.
Reimplemented in BESCmdInterface.
Definition at line 323 of file BESInterface.cc.
void BESInterface::report_request | ( | ) | [protected, virtual, inherited] |
Report the request and status of the request to BESReporterList::TheList().
If interested in reporting the request and status of the request then one must register a BESReporter with BESReporterList::TheList().
If no BESReporter objects are registered then nothing happens.
Definition at line 339 of file BESInterface.cc.
References BESInterface::_dhi, BESDEBUG, DATA_REQUEST, BESReporterList::report(), and BESReporterList::TheList().
Here is the call graph for this function:
void BESInterface::end_request | ( | ) | [protected, virtual, inherited] |
End the BES request.
This method allows developers to add callbacks at the end of a request, to do any cleanup or do any extra work at the end of a request
Definition at line 359 of file BESInterface.cc.
References BESInterface::_dhi, BESDEBUG, _BESDataHandlerInterface::data, and DATA_REQUEST.
void BESInterface::clean | ( | ) | [protected, virtual, inherited] |
Clean up after the request.
Reimplemented in BESCmdInterface.
Definition at line 373 of file BESInterface.cc.
References BESInterface::_dhi, and _BESDataHandlerInterface::response_handler.
Referenced by BESCmdInterface::clean(), and ~BESCgiInterface().
int BESInterface::execute_request | ( | const string & | from | ) | [virtual, inherited] |
Executes the given request to generate a specified response object.
Execute the request by: 1. initializing BES 2. validating the request, make sure all elements are present 3. build the request plan (ie filling in the BESDataHandlerInterface) 4. execute the request plan using the BESDataHandlerInterface 5. transmit the resulting response object 6. log the status of the execution 7. notify the reporters of the request 8. end the request, which allows developers to add callbacks to notify them of the end of the request
If an exception is thrown in any of these steps the exception is handed over to the exception manager in order to generate the proper response.
Reimplemented in BESCmdInterface.
Definition at line 110 of file BESInterface.cc.
References BESInterface::_dhi, BESInterface::build_data_request_plan(), _BESDataHandlerInterface::data, DATA_REQUEST, BESInterface::execute_data_request_plan(), BESInterface::initialize(), BESInterface::invoke_aggregation(), REQUEST_FROM, SERVER_PID, BESLog::TheLog(), and BESInterface::validate_data_request().
Referenced by BESCmdInterface::execute_request().
Here is the call graph for this function:
void BESInterface::add_init_callback | ( | p_bes_init | init | ) | [static, inherited] |
Definition at line 180 of file BESInterface.cc.
void BESInterface::add_end_callback | ( | p_bes_end | end | ) | [static, inherited] |
Definition at line 348 of file BESInterface.cc.
BESDataHandlerInterface BESInterface::_dhi [protected, inherited] |
Definition at line 134 of file BESInterface.h.
Referenced by BESCgiInterface(), BESCmdInterface::BESCmdInterface(), BESInterface::BESInterface(), BESCmdInterface::build_data_request_plan(), build_data_request_plan(), BESInterface::clean(), BESCmdInterface::clean(), BESInterface::dump(), BESInterface::end_request(), BESInterface::exception_manager(), BESApacheInterface::exception_manager(), BESInterface::execute_data_request_plan(), BESCmdInterface::execute_data_request_plan(), BESInterface::execute_request(), BESInterface::initialize(), BESCmdInterface::initialize(), BESApacheInterface::initialize(), BESInterface::invoke_aggregation(), BESCmdInterface::invoke_aggregation(), BESCmdInterface::log_status(), BESInterface::report_request(), BESInterface::transmit_data(), and BESCmdInterface::transmit_data().
BESTransmitter* BESInterface::_transmitter [protected, inherited] |
Definition at line 135 of file BESInterface.h.
Referenced by BESCgiInterface(), BESCmdInterface::build_data_request_plan(), BESInterface::dump(), BESCmdInterface::initialize(), BESInterface::transmit_data(), and ~BESCgiInterface().