X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Ffrontend.xml;h=2350af3ef892eda070163d754a273cf5543e165e;hb=acf66fb3406fb7eb3e8c76cbe073cbe061080a5a;hp=7ab9e8381af2f7c276669d64f7e0999ee36cd42f;hpb=02e5bbc0d685b1f565cbd71bc7c61858e74c4382;p=yaz-moved-to-github.git diff --git a/doc/frontend.xml b/doc/frontend.xml index 7ab9e83..2350af3 100644 --- a/doc/frontend.xml +++ b/doc/frontend.xml @@ -1,4 +1,4 @@ - + Generic server Introduction @@ -13,7 +13,7 @@ If you have a database system that you would like to make available by - means of Z39.50, SRW o SRU, &yaz; basically offers your two options. You + means of Z39.50 or SRU, &yaz; basically offers your two options. You can use the APIs provided by the &asn;, &odr;, and &comstack; modules to create and decode PDUs, and exchange them with a client. @@ -99,6 +99,10 @@ Result-Set Sort (optional). + + Return Explain for SRU (optional). + + @@ -332,8 +336,8 @@ bend_initresult (*bend_init)(bend_initrequest *r); - This handler is also called when operating in SRW/SRU mode - when - a connection has been made (even though SRW/SRU does not offer + This handler is also called when operating in SRU mode - when + a connection has been made (even though SRU does not offer this service). @@ -372,6 +376,8 @@ typedef struct bend_initrequest /* character set and language negotiation - see include/yaz/z-charneg.h */ Z_CharSetandLanguageNegotiation *charneg_request; Z_External *charneg_response; + int (*bend_srw_explain)(void *handle, bend_explain_rr *rr); + int (*bend_srw_scan)(void *handle, bend_scan_rr *rr); } bend_initrequest; typedef struct bend_initresult @@ -458,6 +464,7 @@ typedef struct { int hits; /* number of hits */ int errcode; /* 0==OK */ char *errstring; /* system error string or NULL */ + Z_OtherInformation *search_info; } bend_search_rr; @@ -496,8 +503,8 @@ typedef struct { The bend_search handler is also called when - the frontend server receives a SRW/SRU SearchRetrieveRequest. - For SRW/SRU, a CQL query is usually provided by the client. + the frontend server receives a SRU SearchRetrieveRequest. + For SRU, a CQL query is usually provided by the client. The CQL query is available as part of Z_Query structure (note that CQL is now part of Z39.50 via an external). To support CQL in existing implementations that only do Type-1, @@ -508,8 +515,8 @@ typedef struct { To maintain backwards compatibility, the frontend server of yaz always assume that error codes are BIB-1 diagnostics. - For SRW/SRU operation, a Bib-1 diagnostic code is mapped to - SRW/SRU diagnostic. + For SRU operation, a Bib-1 diagnostic code is mapped to + SRU diagnostic. @@ -541,7 +548,7 @@ typedef struct bend_fetch_rr { The frontend server calls the bend_fetch handler when it needs database records to fulfill a Z39.50 Search Request, a - Z39.50 Present Request or a SRW SearchRetrieveRequest. + Z39.50 Present Request or a SRU SearchRetrieveRequest. The setname is simply the name of the result set that holds the reference to the desired record. The number is the offset into the set (with 1 @@ -559,11 +566,11 @@ typedef struct bend_fetch_rr { - If a SRW/SRU SearchRetrieveRequest is received by the frontend server, + If a SRU SearchRetrieveRequest is received by the frontend server, the referenceId is NULL and the request_format (transfer syntax) is XML (OID name VAL_TEXT_XML). - The schema for SRW/SRU is stored in both the + The schema for SRU is stored in both the Z_RecordComposition structure and schema (simple string). @@ -715,8 +722,21 @@ typedef struct bend_scan_rr { bend_scan_status status; int errcode; char *errstring; + char *scanClause; /* CQL scan clause */ } bend_scan_rr; + + This backend server handles both Z39.50 scan + and SRU scan. In order for a handler to distinguish between SRU (CQL) scan + Z39.50 Scan , it must check for a non-NULL value of + scanClause. + + + + if designed today, it would be a choice using a union or similar, + but that would break binary compatibility with existing servers. + + @@ -776,16 +796,15 @@ typedef struct bend_scan_rr { - The server will accept Z39.50 requests and offer SRW/SRU service - on port 210. + The server will accept Z39.50 requests and offer SRU service on port 210. - Setting up Apache as SRW/SRU Frontend + Setting up Apache as SRU Frontend - If you use Apache + If you use Apache as your public web server and want to offer HTTP port 80 access to the YAZ server on 210, you can use the - + ProxyPass directive. If you have virtual host @@ -796,7 +815,7 @@ typedef struct bend_scan_rr { ErrorLog /home/srw/logs/error_log TransferLog /home/srw/logs/access_log ProxyPass / http://srw.mydomain:210/ - </VirualHost> + </VirtualHost> @@ -814,8 +833,8 @@ typedef struct bend_scan_rr { - Virtual hosts - &gfs-virtual; + Virtual Hosts + &gfs-virtual;