Bug 124385 (DEFECT000312975) - CLib based NLMs may failed to call some LDAP functions.
Summary: CLib based NLMs may failed to call some LDAP functions.
Status: VERIFIED FIXED
Alias: DEFECT000312975
Product: NDS SDK
Classification: Novell Products
Component: LDAP C SDK (show other bugs)
Version: OCT 2006 NDK
Hardware: Other NetWare Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Jeff Vincent
QA Contact: Sundar Swamy
URL:
Whiteboard:
Keywords: English
Depends on:
Blocks:
 
Reported: 2002-09-10 21:42 UTC by Alexander Danoyan
Modified: 2007-05-14 17:49 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rajkumar V 2005-10-10 22:54:49 UTC


------- Bug moved to this database by vrajkumar@novell.com 2005-10-10 16:54 -------

This bug previously known as bug DEFECT000312975 at remedy/
remedy/show_bug.cgi?id=DEFECT000312975
Originally filed under the NDS SDK product and LDAP C SDK component.

---------
<remedy_version_found_in> BLANK </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> CLib based NLMs may failed to call some LDAP functions.
This is the result of LDAP moving to LIBC. The CLIB API SetThreatGroupID()
(NOP) is ignored
and default settings are enforced by LDAPSDK. </remedy_details>
---------
<remedy_notes> dsward (  9/11/2002 1:56:16 PM  Testing -  ) /* If LibC
      based, we still need to support Clib librares
       * that wrap our calls and export their own functions.  Many
       * Clib Libraries migrate incoming threads into their context with
       * SetThreadGroupID.
       *
       * ex:
       *     FooAPI()
       *     {
       *        orgCtx = SetThreadGroupID(myCtx); (migrate to my context)
       *
       *            (do work - call ldap apis )
       *
       *        SetThreadGroupID(orgCtx);  (migrate back)
       *     }
       *
       * This architecture causes problems when we are LibC based
       * because LibC doesn't understand the migration that occurred
       * inside FooAPI above us.  To get around this problem we'll detect
       * if the thread is a Clib Thread and call the appropriate Clib
       * library routines which understand the migration.
       *
       *
      */


 </remedy_notes>