Design: Limit Response Sizes: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(New page: Limiting the response sizes for different classes of users will need to be a configuration parameter. This will be set in the OLFS. Users will initially be divided into two groups: authent...)
 
No edit summary
Line 1: Line 1:
Limiting the response sizes for different classes of users will need to be a configuration parameter. This will be set in the OLFS. Users will initially be divided into two groups: authenticated and unauthenticated. Authenticated users will have unlimited access capability while unauthenticated users will only be allowed to transfer up to ''N'' bytes of data.
Limiting the response sizes for different classes of users will need to be a configuration parameter. This will be set in the OLFS. Users will initially be divided into two groups: authenticated and unauthenticated. Authenticated users will have unlimited access capability while unauthenticated users will only be allowed to transfer up to ''N'' bytes of data.
=== OLFS and BES communication ===
Use a SetContext element in the GetData request.
=== libdap implementation ===
In the class DDS add ''set_'' and ''get_response_limit()'' methods. The ''set-response_limit()'' method will be called by the BES in the ''void
BESDataResponseHandler::execute( BESDataHandlerInterface &dhi )'' or equivalent method.
In the ''libdap:ResponseBuilder'' class

Revision as of 19:31, 30 May 2011

Limiting the response sizes for different classes of users will need to be a configuration parameter. This will be set in the OLFS. Users will initially be divided into two groups: authenticated and unauthenticated. Authenticated users will have unlimited access capability while unauthenticated users will only be allowed to transfer up to N bytes of data.

OLFS and BES communication

Use a SetContext element in the GetData request.

libdap implementation

In the class DDS add set_ and get_response_limit() methods. The set-response_limit() method will be called by the BES in the void BESDataResponseHandler::execute( BESDataHandlerInterface &dhi ) or equivalent method.

In the libdap:ResponseBuilder class