1 Possible compatibility problems with earlier versions marked with '*'.
5 Added VisibleString field body type to GRS-1. It is illegal acc. to my copy
6 of the protocol and it cannot be selected when encoding (maps into 'string'
7 when decoding). Needed to talk to some servers.
9 Demo client can request simple element set names.
13 Fixed bug in the frontend-server. The numberOfRecordsReturned field was
14 handled incorrectly when records were requested in the searchResponse. This
15 will only affect you if you use the frontend-server.
17 Added Explain encoders/decoders to the service-level API. Untested.
19 Added GRS-1 encoders/decoders to the service-level API. Lightly tested.
20 Test-client will ask for and print GRS1. Ztest will return dummy records
23 Added Extended Services: Item Order encoders and decoders to the Service-
24 level API. Untested. Would anyone be willing to fax or mail the pertinent
25 bits of the ILL protocol to us?
27 Moved pretty-printing of structure-wrappers ({..}) from odr_seq.c to
28 odr_cons.c, which causes a more correct output.
30 Fixed handling of searchRequest in frontend server. NextResultSetPosition
31 was always set to 0 when no records were requested in the searchRequest.
33 * Added better external-handling. This shouldn't harm old code that *encodes*
34 externals. It can break code that looks for a 'single-ASN1-type'
35 representation, since those types that are known are now decoded
36 immediately. Look at the SUTRS sample code in seshigh.c and client.c.
37 Documentation updated.
39 Better, but backwards-compatible handling of records in bend_fetchresponse.
40 Length -1 marks structured record, type is deduced from format field.
43 Fairly quick maintenance release to add SUTRS support.
45 Fixed handling of SUTRS records in the demonstration client.
47 * Added format field to the bend_fetchrequest and bend_fetchresponce
48 structures of the backend API (frontend server). When the record is
49 returned, the value of the format field is mapped to an OID. The
50 value VAL_SUTRS will also cause a slightly different ASN.1 packaging
51 of the record. The special value VAL_NONE in the bend_request means
52 that no specific format was requested by the client. Documentation
53 updated accordingly. Test server (ztest) will return a fixed dummy
54 SUTRS record if your client requests SUTRS.
56 Documentation updated accordingly.
58 You can now set external libraries and RANLIB support in the top-level