Hi
I'm writing an overlay which it's principal function is being called on 'modify' operation. This function basically see if a given attribute is being modified. If so, it pass it's value to an external daemon through an unix domain socket to store this value in an external database.
Of course, when the 'modify' callback ends with SLAP_CB_CONTINUE, the operation continues and the new value is committed to background. This is my problem, I don't want to really modify the attribute value at background....
So, Is there a way to 'abort' modify operation in my overlay without stopping to pass control to other overlays? I saw there's others return values from callbacks, as SLAP_CB_BYPASS and SLAP_CB_FREEME but I'm not sure about it... I guess SLAP_CB_BYPASS do the trick, but I'm not sure.
Thanks a lot in advance Lucas Brasilino
Hi Lucas,
I think you should post your question on openldap-devel list instead of openldap-technical.
On Wed, Aug 25, 2010 at 8:43 AM, Lucas Brasilino lucas.brasilino@gmail.comwrote:
Hi
I'm writing an overlay which it's principal function is being called on 'modify' operation. This function basically see if a given attribute is being modified. If so, it pass it's value to an external daemon through an unix domain socket to store this value in an external database.
Of course, when the 'modify' callback ends with SLAP_CB_CONTINUE, the operation continues and the new value is committed to background. This is my problem, I don't want to really modify the attribute value at background....
So, Is there a way to 'abort' modify operation in my overlay without stopping to pass control to other overlays? I saw there's others return values from callbacks, as SLAP_CB_BYPASS and SLAP_CB_FREEME but I'm not sure about it... I guess SLAP_CB_BYPASS do the trick, but I'm not sure.
Thanks a lot in advance Lucas Brasilino
Thanks,
Matheus Morais
Hi Matheus
I think you should post your question on openldap-devel list instead of openldap-technical.
Maybe. Since is stated at openlda-devel that:
"This mailing list is for engineering discussions regarding the development of OpenLDAP Software (as well as JLDAP and JDBC-LDAP). That is, this list is for discussing the development of code distributed as part of OpenLDAP Software, JLDAP, and JDBC-LDAP packages."
and I know many openldap developers are around, I've decided to post here :)
By the way, taking a look at denyop overlay, It seems that if my 'operation modify callback' returns 0 instead of SLAP_CB_CONTINUE this issue it's resolved. I'll try.
Thanks! Lucas Brasilino
Hi again Lucas,
All right then! You're in the right place, sorry! :P
On Wed, Aug 25, 2010 at 12:04 PM, Lucas Brasilino <lucas.brasilino@gmail.com
wrote:
Hi Matheus
I think you should post your question on openldap-devel list instead of openldap-technical.
Maybe. Since is stated at openlda-devel that:
"This mailing list is for engineering discussions regarding the development of OpenLDAP Software (as well as JLDAP and JDBC-LDAP). That is, this list is for discussing the development of code distributed as part of OpenLDAP Software, JLDAP, and JDBC-LDAP packages."
and I know many openldap developers are around, I've decided to post here :)
By the way, taking a look at denyop overlay, It seems that if my 'operation modify callback' returns 0 instead of SLAP_CB_CONTINUE this issue it's resolved. I'll try.
Thanks! Lucas Brasilino
openldap-technical@openldap.org