bes Updated for version 3.21.1
The Backend Server (BES) is the lower two tiers of the Hyrax data server
BESWWWGetCommand Class Reference
Inheritance diagram for BESWWWGetCommand:
Inheritance graph
Collaboration diagram for BESWWWGetCommand:
Collaboration graph

Public Member Functions

 BESWWWGetCommand (const string &cmd)
 
virtual BESResponseHandlerparse_request (BESTokenizer &tokens, BESDataHandlerInterface &dhi)
 knows how to parse a get request
 

Detailed Description

Definition at line 38 of file BESWWWGetCommand.h.

Constructor & Destructor Documentation

◆ BESWWWGetCommand()

BESWWWGetCommand::BESWWWGetCommand ( const string & cmd)
inline

Definition at line 43 of file BESWWWGetCommand.h.

◆ ~BESWWWGetCommand()

virtual BESWWWGetCommand::~BESWWWGetCommand ( )
inlinevirtual

Definition at line 45 of file BESWWWGetCommand.h.

Member Function Documentation

◆ parse_request()

BESResponseHandler * BESWWWGetCommand::parse_request ( BESTokenizer & tokenizer,
BESDataHandlerInterface & dhi )
virtual

knows how to parse a get request

This class knows how to parse a get request, building a sub response handler that actually knows how to build the requested response object, such as das, dds, data, ddx, etc...

A get request looks like:

get <response_type> for <def_name> [return as <ret_name>;

where response_type is the type of response being requested, for example das, dds, dods. where def_name is the name of the definition that has already been created, like a view into the data where ret_name is the method of transmitting the response. This is optional.

This parse method creates the sub response handler, retrieves the definition information and finds the return object if one is specified.

Parameters
tokenizerholds on to the list of tokens to be parsed
dhistructure that holds request and response information
Exceptions
BESSyntaxUserErrorif there is a problem parsing the request

Definition at line 67 of file BESWWWGetCommand.cc.


The documentation for this class was generated from the following files: