[Date Prev][Date Next] [Chronological] [Thread] [Top]

op->o_private



Just a minor issue, but I've been thinking op->o_private needs to be managed explicitly so that multiple modules can hang data there without interfering with each other. E.g.
typedef struct TaggedList {
struct TaggedList *tl_next;
void *tl_tag; /* A unique identifier */
char data[0];
} TaggedList;


Backends and overlays would union this with their own data and the push items onto op->o_private as needed.

Currently overlays can fake this by pushing a slap_callback instead, so I guess it's not an urgent need. Comments?

--
 -- Howard Chu
 Chief Architect, Symas Corp.  http://www.symas.com
 Director, Highland Sun        http://highlandsun.com/hyc
 OpenLDAP Core Team            http://www.openldap.org/project/