[Date Prev][Date Next]
Re: supporting range retrieval (ITS#3193)
The ;range option extension is horrible and, I think, should
not be implemented. Aside from violating basic protocol
syntaxes (such as use of options not conforming to the
attribute option ABNF), the extension is not truly
optional. That is, a server which implements the ;range
option forces its clients to implement the ;range option.
Lastly, I cannot think of any case where a client desires
to obtain more than no vales but less than all values.
The forced paging does nothing but force extra roundtrips
and data inconsistencies (due intervening modifications).
Anyways, changing DESC_CHAR would be bad as that would
allow slapd(8) to accept and return options (such as
invalid language tags) which didn't conform to the
option ABNF. So, I think that would be bad.
At 09:09 AM 6/20/2004, firstname.lastname@example.org wrote:
>Full_Name: Luke Howard
>Submission from: (NULL) (126.96.36.199)
>I was looking at implementing support for range retrieval in our LinkEngine
>plugin. This shouldn't involve any changes to slapd, however it turns out that
>the '=' and '*' characters are not allowed in attribute tags. I haven't checked
>the RFC here, it wouldn't surprise me if MS are violating it, but is there a way
>we can support this in slapd?
>My hackish patch follows.
>RCS file: /repo/OpenLDAP/pkg/ldap/servers/slapd/slap.h,v
>retrieving revision 1.452.2.21
>diff -u -r1.452.2.21 slap.h
>--- slap.h 16 Jun 2004 21:53:56 -0000 1.452.2.21
>+++ slap.h 20 Jun 2004 16:07:25 -0000
>@@ -142,7 +142,7 @@
> #define RDN_NEEDSESCAPE(c) ((c) == '\\' || (c) == '"')
> #define DESC_LEADCHAR(c) ( ASCII_ALPHA(c) )
>-#define DESC_CHAR(c) ( ASCII_ALNUM(c) || (c) == '-' )
>+#define DESC_CHAR(c) ( ASCII_ALNUM(c) || (c) == '-' || (c) == '=' || (c) ==
> #define OID_LEADCHAR(c) ( ASCII_DIGIT(c) )
> #define OID_SEPARATOR(c) ( (c) == '.' )
> #define OID_CHAR(c) ( OID_LEADCHAR(c) || OID_SEPARATOR(c) )