#include <BESSetContainerResponseHandler.h>
Inheritance diagram for BESSetContainerResponseHandler:
Public Member Functions | |
BESSetContainerResponseHandler (string name) | |
virtual | ~BESSetContainerResponseHandler (void) |
virtual void | execute (BESDataHandlerInterface &dhi) |
executes the command to create a new container or replaces an already existing container based on the provided symbolic name. | |
virtual void | transmit (BESTransmitter *transmitter, BESDataHandlerInterface &dhi) |
transmit the response object built by the execute command using the specified transmitter object | |
virtual void | dump (ostream &strm) const |
dumps information about this object | |
virtual BESResponseObject * | get_response_object () |
return the current response object | |
virtual BESResponseObject * | set_response_object (BESResponseObject *o) |
replaces the current response object with the specified one, returning the current response object | |
virtual const string & | get_name () const |
return the name of this response object | |
Static Public Member Functions | |
static BESResponseHandler * | SetContainerResponseBuilder (string handler_name) |
Protected Attributes | |
string | _response_name |
BESResponseObject * | _response |
This request handler creates a new container, or replaces an already existing container in the specified container storage given the symbolic name, real name (in most cases a file name), and the type of data represented by the real name (e.g. netcdf, cedar, cdf, hdf, etc...) The request has the syntax:
set container in <store_name> values <sym_name>,<real_name>,<data_type>;
It returns whether the container was created or replaces successfully in an informational response object and transmits that response object.
|
|
|
|
|
dumps information about this object Displays the pointer value of this instance
Reimplemented from BESResponseHandler. |
|
executes the command to create a new container or replaces an already existing container based on the provided symbolic name. The symbolic name is first looked up in the specified container storage object, volatile if no container storage name is specified. If the symbolic name already exists (the container already exists) then the already existing container is removed and the new one added using the given real name (usually a file name) and the type of data represented by this container (e.g. cedar, cdf, netcdf, hdf, etc...) An informational response object BESInfo is created to hold whether or not the container was successfully added/replaced. Possible responses are:
Successfully added container "<sym_name>" in container storage "<store_name>"
Implements BESResponseHandler. |
|
return the name of this response object This name is used to determine which response handler can handle a requested responose, such as das, dds, ddx, tab, info, version, help, etc...
|
|
return the current response object Returns the current response object, null if one has not yet been created. The response handler maintains ownership of the response object.
|
|
replaces the current response object with the specified one, returning the current response object This method is used to replace the response object with a new one, for example if during aggregation a new response object is built from the current response object. The caller of set_response_object now owns the returned response object. The new response object is now owned by the response object.
|
|
|
|
transmit the response object built by the execute command using the specified transmitter object If a response object was built then transmit it as text using the specified transmitter object.
Implements BESResponseHandler. |
|
|
|
|